Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

mureo_batch_begin

Start a bulk change batch to tag every action_log entry until the batch ends, enabling review and rollback as one unit. Use before multi-entity passes like exclusions or keyword changes.

Instructions

Declare the start of a bulk change so it can be reviewed and reversed as ONE unit. Every action_log entry recorded until mureo_batch_end — on any platform, native, hosted connector or bridged/plugin — is tagged with the returned batch_id. Call this BEFORE a multi-entity pass (N placement exclusions, N keywords, N ad status changes); afterwards, rollback_plan_get with that batch_id reports what can and cannot be reversed. Refused if a batch is already open.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoOptional path to STATE.json. Defaults to STATE.json in the MCP server's current working directory. Paths outside it are refused.
labelYesWhat this change set is, in the operator's words (e.g. 'exclude low-quality display placements'). Stored with the batch so the id still means something weeks later.
reasonNoWhy this change is being made: one or two sentences naming the evidence and the expected effect. Stored in the journal and on the action_log entry this call produces, for the operator and the next session.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.20.0
    • addedInput schema / properties / reason
      Added value: +{
+  "description": "Why this change is being made: one or two sentences naming the evidence and the expected effect. Stored in the journal and on the action_log entry this call produces, for the operator and the next session.",
+  "maxLength": 500,
+  "type": "string"
+}
  2. Addedv0.10.44

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does it well. It discloses that all action_log entries until mureo_batch_end are tagged, that the call is refused if a batch is already open, that paths outside the working directory are refused, and that the returned id feeds rollback_plan_get. This goes well beyond what the schema or annotations reveal.

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?

The description is dense but every sentence earns its place: the core purpose is front-loaded, usage timing is explicit, platform coverage is clarified, and refusal conditions are stated. No filler or repetition is present.

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

Completeness5/5

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

For a batch-lifecycle tool with no output schema, the description covers what the tool returns (batch_id), how it relates to rollback_plan_get, how long the batch stays open, and when it will refuse. An agent has enough context to call it correctly and follow up appropriately.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents path, label, and reason. The description adds meaning by explaining that label is stored with the batch for later identification and that reason is stored in the journal and on the action_log entry. That is meaningful added context beyond the schema.

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?

The description states a clear verb and resource: declare the start of a bulk change so it can be reviewed/reversed as one unit. It prominently distinguishes this from mureo_batch_end and mureo_batch_status by describing the start semantics and the returned batch_id, so an agent can tell when this tool is the right one.

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?

The description gives strong contextual guidance: call this BEFORE a multi-entity pass, and use rollback_plan_get with the resulting batch_id afterwards. It does not explicitly name alternatives or state when not to use this tool, so it stops short of a 5.

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