Skip to main content
Glama

mureo_state_action_log_append

Append a single workflow action to STATE.json for later evaluation, filling missing baseline metrics from a recent campaign snapshot and returning the updated state.

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). An omitted metrics_at_action is filled from a campaign snapshot fetched within 2 days; the answer's baseline (source / reason) says whether it was. Returns the updated state document.

Input 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), display_title / display_summary — the one line the dashboard shows for this entry — and reason — WHY the change was made, which only this call can supply (see the field). Ops history: expected (what the change should move) and decision_id (an earlier proposal it carried out).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.33.0
    • addedInput schema / properties / entry / properties / evaluation
      Added value: +{
      +  "description": "The evaluation table — pass the ``evaluation`` object ``mureo_outcome_evaluate`` returned, unchanged. Required with ``evaluation_of`` (evaluation_required) and refused without it (evaluation_without_target). Its shape is checked; it is stored where the automatic closure stores its table, so ops history shows the verdict, and the record's ``summary`` is built from it (a passed one is replaced).",
      +  "type": "object"
      +}
    • changedInput schema / properties / entry / properties / evaluation_of / description
      Previous value: -"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."New value: +"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`` with the same ``evaluation_of`` 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. Requires ``evaluation``. The record's ``decision_id`` is the evaluated entry's, whatever is passed."
    • changedInput schema / properties / entry / properties / expected / description
      Previous value: -"What the recorded change should move (e.g. [{\"metric\": \"cpa\", \"direction\": \"down\"}]). With reason, mureo writes the decision record for this change and links the entry to it. Required with reason when ops history is enabled and the entry opens a new decision."New value: +"What the recorded change should move (e.g. [{\"metric\": \"cpa\", \"direction\": \"down\"}]). With several effects, mark exactly one \"primary\": true — the verdict is read off it. With reason, mureo writes the decision record for this change and links the entry to it. Required with reason when ops history is enabled and the entry opens a new decision."
    • addedInput schema / properties / entry / properties / expected / items / properties / primary
      Added value: +{
      +  "description": "The effect the verdict is read off. One effect is primary by itself; with several, mark exactly one.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / entry / properties / metrics_at_action / description
      Added value: +"Baseline metrics. Omit on a campaign change to fill it from that campaign's STATE.json snapshot."
  2. Changed1 schema field changedv0.28.0
    • addedInput schema / properties / entry / properties / approval
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Optional. An external approval this change carried out (recorded and shown, never verified).",
      +  "properties": {
      +    "approved_at": {
      +      "maxLength": 64,
      +      "type": "string"
      +    },
      +    "approved_by": {
      +      "maxLength": 80,
      +      "type": "string"
      +    },
      +    "reference": {
      +      "maxLength": 128,
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "reference",
      +    "approved_by",
      +    "approved_at"
      +  ],
      +  "type": "object"
      +}
  3. Changed3 schema fields changedv0.26.0
    • 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), the provenance trio origin / external_id / occurred_at for a change mureo did NOT make (see those fields), display_title / display_summary — the one line the dashboard shows for this entry — and reason — WHY the change was made, which only this call can supply (see the field)."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), display_title / display_summary — the one line the dashboard shows for this entry — and reason — WHY the change was made, which only this call can supply (see the field). Ops history: expected (what the change should move) and decision_id (an earlier proposal it carried out)."
    • addedInput schema / properties / entry / properties / decision_id
      Added value: +{
      +  "description": "Optional. The decision_id of an earlier proposed or adopted decision this change carried out; a proposal becomes adopted. Omit it otherwise — mureo creates the decision itself.",
      +  "maxLength": 128,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / entry / properties / expected
      Added value: +{
      +  "description": "What the recorded change should move (e.g. [{\"metric\": \"cpa\", \"direction\": \"down\"}]). With reason, mureo writes the decision record for this change and links the entry to it. Required with reason when ops history is enabled and the entry opens a new decision.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "direction": {
      +        "enum": [
      +          "up",
      +          "down",
      +          "hold"
      +        ],
      +        "type": "string"
      +      },
      +      "horizon_days": {
      +        "maximum": 365,
      +        "minimum": 1,
      +        "type": "integer"
      +      },
      +      "metric": {
      +        "enum": [
      +          "cpa",
      +          "cpc",
      +          "cpl",
      +          "cpm",
      +          "conversions",
      +          "cvr",
      +          "ctr",
      +          "roas",
      +          "cost",
      +          "spend",
      +          "clicks",
      +          "impressions"
      +        ],
      +        "type": "string"
      +      },
      +      "target": {
      +        "type": "number"
      +      }
      +    },
      +    "required": [
      +      "metric",
      +      "direction"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 12,
      +  "type": "array"
      +}
  4. Changed2 schema fields changedv0.20.0
    • 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), 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."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), display_title / display_summary — the one line the dashboard shows for this entry — and reason — WHY the change was made, which only this call can supply (see the field)."
    • addedInput schema / properties / entry / properties / reason
      Added value: +{
      +  "description": "WHY this change was made — one or two sentences naming the evidence and the expected effect. SET IT whenever the change you are recording had a reason: unlike every other mutating tool, this one takes no call-level ``reason``, because it RECORDS a change rather than making one, so this field is the only place the rationale can go. Leave it out only for an entry that genuinely had none. Refused rather than truncated when over the bound.",
      +  "maxLength": 500,
      +  "minLength": 1,
      +  "type": "string"
      +}
  5. 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"
      +}
  6. 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"
      +}
  7. 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"
      +}
  8. 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"
      +]
  9. Addedv0.9.12
  10. Removedv0.9.6
  11. Addedv0.9.2
  12. Removedv0.9.1
  13. Addedv1.0.6

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and discloses meaningful traits: atomicity, automatic metrics_at_action backfill from a snapshot fetched within 2 days, the baseline provenance in the answer, and that it returns the updated state document. It omits operational details such as refusal modes and idempotency, but the core behavioral profile is unusually well surfaced for a bare description.

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 tight sentences, front-loaded with the core action and immediately followed by the use case and the notable auto-fill behavior. Every sentence contributes information and there is no boilerplate.

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 complex nested-entry append tool with no output schema, the description covers purpose, usage, a key automatic behavior, and the return value. The schema is exceptionally rich and carries the detailed field rules, so the description does not need to duplicate them; a little more on refusal or idempotency behavior would make it complete.

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%, so the schema already documents the two top-level parameters and the nested entry fields in depth. The description adds useful context about the automatic metrics_at_action snapshot fill, but it does not explain entry field semantics beyond what the schema provides, matching the baseline 3 for high-coverage schemas.

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

Purpose4/5

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

The description states a specific verb-resource pair: atomically appending a single action_log entry to STATE.json. It is clearly distinct from read-only state tools, but it never names or contrasts a sibling such as mureo_state_upsert_campaign or mureo_decision_record, so it stops short of the explicit differentiation required for a 5.

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?

It gives a clear use condition — whenever a workflow takes an action that should be evaluable later — with concrete examples like budget changes, campaign pauses, and negative-keyword adds. It does not state when not to use it or point to alternatives, so the guidance is clear but not exhaustive.

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

Deploy Server

Other Tools