Skip to main content
Glama

Results of applied changes

change_results
Read-only

Shows what applied Google Ads changes did before vs after using Google's own numbers, covering negatives, pauses, budgets, bidding, and new campaigns, ad groups, and keywords.

Instructions

What applied Google Ads changes did, before vs after, from Google's numbers: negatives (what the searches they block cost), pauses (what it spent; the rest of its campaign), budgets, bidding and enabling (the campaign), and new campaigns, ad groups and keywords (since added). Ready 7 days after applying (change_history says when). Offer it when the user returns to an account with results ready, and give each reading with the caveats.

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": {
      "customer_id": "<customer_id>"
    },
    "name": "change_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMost proposals to measure
customer_idYesGoogle Ads customer ID, with or without dashes (from list_accounts)
proposal_idNoOne applied proposal; omit for the latest

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.35.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, closed-world; the description adds the material behavior an agent needs: a 7-day maturation delay, per-category semantics (pauses report what it spent and the rest of its campaign, negatives report what blocked searches cost), and an instruction to present each reading with caveats. It does not describe response shape or pagination, but the caveat and timing disclosures are the valuable part.

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

Conciseness3/5

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

The single long sentence packing all change types is dense and parenthetical-heavy, making it slower to parse than necessary. It is information-dense and front-loaded with the core purpose, but the enumerated categories could be bulleted or trimmed without losing value.

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 3-parameter read-only tool with no output schema, the description covers what is measured, when results exist, and how to present them (with caveats). It doesn't explain what happens on a partial match or what a response looks like, but the timing guidance and caveat instruction cover the main risks in calling it.

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 baseline would be 3; the description adds meaning to limit ('Most proposals to measure') by framing the call as measuring applied proposals, and clarifies proposal_id default behavior is covered in schema. The phrasing 'Most proposals to measure' implicitly links limit to proposals, slightly strengthening 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?

States a specific verb+resource: it reports what applied Google Ads changes did, before vs after, using Google's numbers. It then enumerates the change types covered (negatives, pauses, budgets, bidding, enabling, new campaigns/ad groups/keywords), which makes the scope distinguishable from change_history and undo_changes.

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?

Explicit about readiness ('Ready 7 days after applying') and names the sibling that answers the timing question ('change_history says when'). It also gives a trigger condition ('Offer it when the user returns to an account with results ready'). It lacks an explicit exclusion, e.g. what to do for changes younger than 7 days beyond the pointer to change_history.

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