Skip to main content
Glama

mureo_state_action_log_append

Append an action log entry to STATE.json for any workflow action that must be evaluated later, such as budget changes or campaign pauses. Returns the updated state document.

Instructions

Atomically append a single action_log entry to STATE.json. Use this whenever a workflow takes an action that should be evaluable later (budget changes, campaign pauses, negative-keyword adds). Returns the updated state document.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoOptional path to the file. Defaults to STRATEGY.md / STATE.json in the MCP server's current working directory. Paths outside cwd are refused.
entryYesAn action_log entry. Required: action (short description), platform (google_ads / meta_ads / etc.). The ``timestamp`` is stamped by the server — do not compute it. Optional: campaign_id, ad_id, entity_type, entity_id, summary, command, metrics_at_action, observation_due, reversible_params, rollback_of, evaluation_of, batch_id (normally stamped by the server — see the field), the provenance trio origin / external_id / occurred_at for a change mureo did NOT make (see those fields), and display_title / display_summary — the one line the dashboard shows for this entry.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.17.1
    • changedInput schema / properties / entry / description
      Previous value: -"An action_log entry. Required: action (short description), platform (google_ads / meta_ads / etc.). The ``timestamp`` is stamped by the server — do not compute it. Optional: campaign_id, ad_id, entity_type, entity_id, summary, command, metrics_at_action, observation_due, reversible_params, rollback_of, evaluation_of, batch_id (normally stamped by the server — see the field), and the provenance trio origin / external_id / occurred_at for a change mureo did NOT make (see those fields)."New value: +"An action_log entry. Required: action (short description), platform (google_ads / meta_ads / etc.). The ``timestamp`` is stamped by the server — do not compute it. Optional: campaign_id, ad_id, entity_type, entity_id, summary, command, metrics_at_action, observation_due, reversible_params, rollback_of, evaluation_of, batch_id (normally stamped by the server — see the field), the provenance trio origin / external_id / occurred_at for a change mureo did NOT make (see those fields), and display_title / display_summary — the one line the dashboard shows for this entry."
    • addedInput schema / properties / entry / properties / display_summary
      Added value: +{
      +  "description": "One sentence under the title, still for the operator. Plain text — no markdown: ``**bold**`` is shown to a person as asterisks. Keep the full reasoning in ``summary``, which nothing here shortens. ``display_title`` and ``display_summary`` are the ONE LINE the dashboard shows for this entry: title at most 40 characters, summary at most 120. Over either bound the append is refused, never truncated. They do not replace ``summary`` — write that as fully as the next agent needs; these two are what an operator reads at a glance.",
      +  "maxLength": 120,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / entry / properties / display_title
      Added value: +{
      +  "description": "What this action WAS, in a few words an operator reads on a dashboard row — 'Paused two losing ad groups'. ``display_title`` and ``display_summary`` are the ONE LINE the dashboard shows for this entry: title at most 40 characters, summary at most 120. Over either bound the append is refused, never truncated. They do not replace ``summary`` — write that as fully as the next agent needs; these two are what an operator reads at a glance.",
      +  "maxLength": 40,
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. Changed6 schema fields changedv0.10.44
    • addedInput schema / properties / entry / dependentRequired / external_id
      Added value: +[
      +  "origin"
      +]
    • changedInput schema / properties / entry / description
      Previous value: -"An action_log entry. Required: action (short description), platform (google_ads / meta_ads / etc.). The ``timestamp`` is stamped by the server — do not compute it. Optional: campaign_id, ad_id, entity_type, entity_id, summary, command, metrics_at_action, observation_due, reversible_params, rollback_of, evaluation_of."New value: +"An action_log entry. Required: action (short description), platform (google_ads / meta_ads / etc.). The ``timestamp`` is stamped by the server — do not compute it. Optional: campaign_id, ad_id, entity_type, entity_id, summary, command, metrics_at_action, observation_due, reversible_params, rollback_of, evaluation_of, batch_id (normally stamped by the server — see the field), and the provenance trio origin / external_id / occurred_at for a change mureo did NOT make (see those fields)."
    • addedInput schema / properties / entry / properties / batch_id
      Added value: +{
      +  "description": "Normally OMIT this. While a batch is open (mureo_batch_begin) the server stamps the entry with it automatically, so a bulk pass groups itself. Supplying it is an explicit ASSERTION that this entry belongs to that batch, and it is validated: the id must name a declared batch that is still open. An unknown id, or one whose batch has been closed, is REFUSED — membership cannot be invented, and a closed batch's reported member count cannot be made false after the fact. To group imported or backfilled history, open a batch for the import rather than reattaching to an old one.",
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / entry / properties / external_id
      Added value: +{
      +  "description": "The change feed's own identifier for an external change, so recording it twice is a no-op. Requires origin='external'. Namespace it with the platform key (e.g. 'tiktok_ads|<change id>'). Omit only when the feed exposes no id — the entry is then recorded, but a later pass cannot recognise it and will record it again.",
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / entry / properties / occurred_at
      Added value: +{
      +  "description": "ISO 8601 time the PLATFORM says the change happened — history, never 'now'. Unlike ``timestamp`` (which the server always stamps) this is accepted, because the change's own date is not something the server can know. The observation window anchors on it, so a change made two weeks ago is already due for review rather than due in a fortnight.",
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / entry / properties / origin
      Added value: +{
      +  "description": "OMIT for anything mureo did — that is what an absent origin means. Set 'external' ONLY for a change mureo did not make, which you read out of a platform's own change history (typically a hosted connector mureo cannot poll itself; native and plugin platforms are covered by mureo_external_changes_import). An external entry is permanently marked as observed rather than performed: mureo will refuse to plan a rollback for it, because it never saw the prior value. Never use it to record a change you made through mureo.",
      +  "enum": [
      +    "external"
      +  ],
      +  "type": "string"
      +}
  3. Changed4 schema fields changedv0.10.43
    • addedInput schema / properties / entry / dependentRequired
      Added value: +{
      +  "entity_id": [
      +    "entity_type"
      +  ],
      +  "entity_type": [
      +    "entity_id"
      +  ]
      +}
    • changedInput schema / properties / entry / description
      Previous value: -"An action_log entry. Required: action (short description), platform (google_ads / meta_ads / etc.). The ``timestamp`` is stamped by the server — do not compute it. Optional: campaign_id, ad_id, summary, command, metrics_at_action, observation_due, reversible_params, rollback_of, evaluation_of."New value: +"An action_log entry. Required: action (short description), platform (google_ads / meta_ads / etc.). The ``timestamp`` is stamped by the server — do not compute it. Optional: campaign_id, ad_id, entity_type, entity_id, summary, command, metrics_at_action, observation_due, reversible_params, rollback_of, evaluation_of."
    • addedInput schema / properties / entry / properties / entity_id
      Added value: +{
      +  "description": "Platform id of the entity_type target. Record the pair so a later run can avoid repeating a change to that same entity.",
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / entry / properties / entity_type
      Added value: +{
      +  "description": "Generic target kind for a sub-campaign action, such as ad_group, ad_set, or placement. Use together with entity_id.",
      +  "minLength": 1,
      +  "type": "string"
      +}
  4. Changed7 schema fields changedv0.10.37
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / entry / description
      Previous value: -"An action_log entry. Required: timestamp (ISO 8601), action (short description), platform (google_ads / meta_ads / etc.). Optional: campaign_id, summary, command, metrics_at_action, observation_due, reversible_params, rollback_of."New value: +"An action_log entry. Required: action (short description), platform (google_ads / meta_ads / etc.). The ``timestamp`` is stamped by the server — do not compute it. Optional: campaign_id, ad_id, summary, command, metrics_at_action, observation_due, reversible_params, rollback_of, evaluation_of."
    • addedInput schema / properties / entry / properties / ad_id
      Added value: +{
      +  "description": "The ad this action targeted, for ad-level actions (pause / enable / creative swap). Record it so a later run can tell an ad mureo stopped from one an operator stopped by hand.",
      +  "type": "string"
      +}
    • addedInput schema / properties / entry / properties / evaluation_of
      Added value: +{
      +  "description": "Positional index (into the full action_log) of the action whose ``observation_due`` this entry evaluates and CLOSES. Append this after running ``mureo_outcome_evaluate`` on a past-due observation so the source entry leaves the pending set (``mureo_outcome_evaluate`` is pure and records nothing itself). Must point at an existing entry — the daily-check's pending scope reads the returned ``index`` field to fill it.",
      +  "type": "integer"
      +}
    • addedInput schema / properties / entry / properties / rollback_of / description
      Added value: +"Positional index (into the full action_log) of the action this entry reverses. Normally written by the rollback surface (``rollback_apply``), not by hand. Must point at an existing entry."
    • addedInput schema / properties / entry / properties / timestamp / description
      Added value: +"IGNORED — the server stamps the entry with its own clock (ISO 8601 with UTC offset). Accepted only for backward compatibility with existing callers; any value supplied here is discarded, so a drifted client date can never be persisted and later read back as evidence of 'today'."
    • changedInput schema / properties / entry / required
      Previous value: -[
      -  "timestamp",
      -  "action",
      -  "platform"
      -]New value: +[
      +  "action",
      +  "platform"
      +]
  5. Addedv0.9.12
  6. Removedv0.9.6
  7. Addedv0.9.2
  8. Removedv0.9.1
  9. Addedv1.0.6

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the burden and delivers real behavioral context: atomicity, the single-entry constraint, the write target (STATE.json), and the return contract ('Returns the updated state document'). It doesn't explicitly flag this as a mutation, but 'append' makes that self-evident, and the schema's field notes (server-stamped timestamp, batch validation refusals) add further depth around it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences with zero waste: operation first, usage trigger second, return value third. The most decision-relevant facts are front-loaded and every sentence earns its place. The verbose schema is separate, so the description itself is appropriately tight.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a nested-object, 2-parameter tool with no output schema and no annotations, the description covers operation, trigger, atomicity, and return in just three sentences while the schema documents every field in depth. The only notable gap is that the description doesn't point to related logging workflows (batch tools, external_changes_import) that an agent might otherwise need to discover via field-level notes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the field descriptions are unusually rich (origin trio semantics, discarded timestamp, batch_id validation, display length refusal), so the schema fully carries parameter meaning. The description adds only illustrative action examples, no new parameter semantics, so the high-coverage baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource ('Atomically append a single action_log entry to STATE.json') that names the target file, the operation, and the atomicity guarantee. The examples (budget changes, campaign pauses, negative-keyword adds) plus the distinct action_log scope clearly differentiate it from sibling state tools like mureo_state_get and mureo_state_set.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger condition ('whenever a workflow takes an action that should be evaluable later') with concrete examples, which is clear context for when to call it. It does not explicitly name excluded cases or route to alternatives such as mureo_external_changes_import for externally-observed changes, though that distinction is handled inside the schema's origin field.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools