list_action_logs
list_action_logs MCP tool: read the project's action log (optimizations performed, with dates) to build monthly reports and correlate actions with AI visibility changes.
Updated 2026-06-03
list_action_logs
list_action_logs returns the project's action log: the journal of optimizations performed on the project (page rewrites, published content, outreach, technical fixes). Each entry carries a title, an optional description, the day the action was performed, and a source flag telling whether it was logged from the Mentionable app or by an AI agent through create_action_log.
When to use
Use it whenever the user asks "what did we do this month?" or wants a monthly report. Filter by date range to pull exactly one billing period, then combine with list_prompts stats to show what was done and what it changed. It is also the right tool for before/after analysis: fetch the actions of the last 60 days, compare visibility between the period before and after each action, and attribute movements in mentions to concrete work.
Input
| Field | Type | Default | Description |
|---|---|---|---|
projectId |
string (CUID) | required | Project whose action log to read. |
cursor |
string | none | Pagination cursor from a previous call (pageInfo.nextCursor). |
limit |
number | 20 | Page size, 1 to 100. |
filters.from |
string | none | Only actions performed on or after this day (YYYY-MM-DD). |
filters.to |
string | none | Only actions performed on or before this day (YYYY-MM-DD). |
sortBy |
enum | recent |
recent (newest first) or oldest (chronological). |
Response
Standard paginated shape. date is the day the action was performed (can be backdated by the user), createdAt is when the entry was written. source is app for entries logged manually in the dashboard and mcp for entries logged by an AI agent.
{
"data": [
{
"id": "clxaction001",
"title": "Optimized /pricing page",
"description": "Rewrote the H1, added FAQ schema markup, tightened the comparison table.",
"date": "2026-05-12",
"source": "app",
"createdAt": "2026-05-12T10:00:00.000Z"
},
{
"id": "clxaction002",
"title": "Published comparison article vs Otterly",
"description": null,
"date": "2026-05-05",
"source": "mcp",
"createdAt": "2026-05-05T16:42:11.000Z"
}
],
"pageInfo": { "hasMore": false, "nextCursor": null, "totalCount": 2 },
"summary": { "totalActions": 2 }
}
Tips and patterns
- Monthly report: call once with
filters.from/filters.toset to the first and last day of the month,sortBy: "oldest"to get a chronological narrative. - Impact analysis: for each action, query
list_promptsand compare mention rates before and afterdate. The dashboard performance chart shows the same markers visually. - The log is intentionally raw. No scoring, no classification. The agent reading it brings its own judgment on which actions mattered.
- Entries with
source: "mcp"were logged by an agent. If your workflow both performs and logs actions, deduplicate on title + date before logging again.
Related tools
- create_action_log — log a new action after completing an optimization.
- list_prompts — mention statistics to correlate with logged actions.
- list_page_audits — audits already run on the project, often the action that precedes a page rewrite.