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.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"entry": "<entry>"
},
"name": "mureo_state_action_log_append"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | No | Optional path to the file. Defaults to STRATEGY.md / STATE.json in the MCP server's current working directory. Paths outside cwd are refused. | |
| entry | Yes | 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). |