create_action_log

create_action_log writes a new entry in the project's action log. Call it right after completing a piece of work (optimizing a page, publishing an article, fixing schema markup) so the action is recorded with its date. Logged actions appear in the Activity page of the app, as markers on the dashboard performance chart, and in any monthly report built with list_action_logs.

When to use

Use it as the last step of any agent workflow that changes something for the project. A typical loop: run_page_audit on a URL, apply the modifications, then create_action_log with a title like "Optimized /pricing page from audit". This closes the reporting loop: the user (or their client) sees what was done and when, and can correlate it with mention movements on the chart.

Requires member role minimum, customer role rejected. Entries created here are tagged source: "mcp" so the app shows they were logged by an AI agent.

Input

Field	Type	Default	Description
projectId	string (CUID)	required	Project to log the action on.
title	string	required	Short label of the action, 1 to 200 characters. Name the page or asset touched.
description	string	none	Optional detail, up to 2000 characters. What was changed and why.
date	string	today	Day the action was performed (YYYY-MM-DD). Can be backdated.

Response

Returns the created entry. date is the day of the action, createdAt the write timestamp.

{
  "success": true,
  "actionLog": {
    "id": "clxaction003",
    "title": "Optimized /pricing page from audit",
    "description": "Applied 12 modifications from the page audit: H1 rewrite, FAQ schema, answer-first intro.",
    "date": "2026-06-03",
    "source": "mcp",
    "createdAt": "2026-06-03T14:21:08.000Z"
  }
}

Tips and patterns

• Write titles a client can read in a report: "Optimized /pricing page" beats "edits applied".
• One entry per meaningful action. Batch micro-edits on the same page into a single entry with the detail in description.
• Backdate with date when logging work performed earlier, so the marker lands on the right day on the performance chart.
• Check list_action_logs first if your workflow may re-run: there is no built-in deduplication.

Related tools

• list_action_logs — read the journal back for reporting and impact analysis.
• run_page_audit — the audit that typically precedes the optimization you are logging.
• get_page_audit — the modifications applied, useful material for the description field.