Skip to main content
Glama

mureo_learning_reset_preflight

Pre-flight any ad-platform change to see if it restarts a campaign's automated bidding learning period. Read-only check outputs learning state and guardrail verdict before applying.

Instructions

Pre-flight a pending ad-platform change against the target campaign's learning period. Read-only — it changes nothing and calls no platform API. Returns (1) whether mureo classifies the change as restarting an automated bid strategy's learning period, with the first-party source that classification rests on; (2) the campaign's current learning state as recorded in STATE.json; (3) whether STRATEGY.md ## Guardrails (block_learning_resets / block_learning_resets_during_incident) would refuse it. Call this BEFORE a bid-strategy, budget, conversion-setting, keyword or re-enable change and show the operator the answer in your confirmation step. reset_risk='unknown' and learning_state.state='unknown'/'unreportable' mean mureo does not know — they never mean safe.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argumentsNoThe arguments you are about to pass. Needed because one tool can be both: google_ads_campaigns_update resets learning when it carries bidding_strategy and does not when it only renames the campaign.
tool_nameYesThe tool you are about to call, e.g. 'google_ads_campaigns_update'.
campaign_idNoCampaign whose learning state to look up. Optional when 'arguments' already carries campaign_id; supply it for tools keyed on something else (e.g. google_ads_budget_update takes a budget_id), otherwise the learning state is reported unknown.
Behavior5/5

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

With no annotations provided, the description carries full burden. It clearly states 'Read-only — it changes nothing and calls no platform API', which is a critical behavioral disclosure. It also explains the meaning of 'unknown' values, ensuring the agent doesn't misinterpret them as safe. This exceeds what annotations would typically provide.

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

Conciseness4/5

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

The description is detailed but well-structured: front-loaded with the main purpose, followed by read-only status, return items, when to call, and crucial caveats. Every sentence contributes value, though the length is slightly above average for a tool description.

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?

Despite no output schema and no annotations, the description covers the tool's purpose, usage, behavior, and parameter semantics comprehensively. It describes what is returned (three items), the source of data (STATE.json, STRATEGY.md), and edge cases (unknown values). Minor omissions include exact return format or error handling, but these are not critical for this preflight tool.

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 description coverage is 100%, but the description adds significant meaning beyond the schema. It explains why 'arguments' is needed (same tool can behave differently based on arguments) and when 'campaign_id' is optional. This contextualizes the parameters in a way the schema alone cannot.

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 clearly states the tool's function with a specific verb ('Pre-flight') and resource ('a pending ad-platform change against the target campaign's learning period'). It distinguishes itself from siblings by focusing on pre-flight checks before modifications, which is unique among the listed tools.

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 explicitly states when to use the tool: 'Call this BEFORE a bid-strategy, budget, conversion-setting, keyword or re-enable change'. It also instructs to show the operator the answer in the confirmation step. While it doesn't explicitly state when not to use it or name alternatives, the guidance is clear and actionable.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/logly/mureo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server