Skip to main content
Glama

Honeyfield Marketing MCP

Google Ads: Change history

ads_change_history
Read-only

Änderungshistorie des Kontos: wer hat wann was geändert (User, Ressource, Operation, Felder). Google erlaubt max. 29 Tage zurück; das Fenster schließt heute ein. limit: max. Einträge (1–200), neueste zuerst. workspace: Slug des Kunden-Workspace (optional bei nur einem Workspace).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ads_change_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
limitNo
workspaceNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the read-only/open-world profile, and the description adds real operational context on top: a hard 29-day retention limit that expires daily and newest-first ordering. It does not mention rate limits, pagination, or result volume beyond the limit cap.

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?

Four short sentences, front-loaded with the resource definition before the retention caveat and the two parameter notes. Dense but no filler; the only drag is that the parenthetical field list and the retention clause slightly overlap in intent.

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?

With an output schema present, return values need no explanation, and the read-only profile comes from annotations. What remains for the description — retention window, ordering, the two optional parameters — is mostly covered, with the 'days' parameter range the only clear omission.

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 0%, so the description must compensate. It does explain 'limit' (1–200, newest first) and 'workspace' (optional with a single workspace), but 'days' is never named or bounded — the 29-day cap is stated only as a Google constraint, not as the valid range for the days parameter (default 14).

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 ('Änderungshistorie des Kontos') and enumerates the returned dimensions (User, Ressource, Operation, Felder). No sibling tool in the ads_* family covers change auditing, so the agent can distinguish it immediately from performance/list tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied through the 29-day retention constraint ('das Fenster schließt heute ein'), which tells the agent when data is still retrievable, but it never says when to prefer this tool over alternatives or what it is not for (e.g., vs. ads_campaign_performance for metric history).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources