Skip to main content
Glama

MetricPort

Change history

ads_change_history
Read-onlyIdempotent

Who changed what in the account in the last N days (max 30): resource type, operation, user, timestamp. Explains sudden performance shifts.

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": {
      "property": "<property>"
    },
    "name": "ads_change_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
limitNo
propertyYesGoogle Ads customer id from list_properties, e.g. 1234567890

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the returned data shape, which is genuinely useful, but the "max 30" cap merely repeats the schema's maximum=30 and it says nothing about pagination or the limit behavior.

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?

Two tight clauses, front-loaded with the core capability before the diagnostic value. Only the redundant "(max 30)" is wasted given the schema already encodes that bound.

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 simple read-only tool with no output schema, the description adequately conveys the returned dimensions and the time-window cap. Missing pagination/limit behavior is the main residual gap, which is minor given the safety annotations.

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 coverage is only 33% -- only 'property' is described -- so the description must compensate. It partially explains 'days' ("last N days") but says nothing about 'limit' (default 200, max 1000), leaving one parameter undocumented in both places.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: it surfaces who changed what in the account, and enumerates the returned fields (resource type, operation, user, timestamp). This is clearly distinct from every sibling, none of which cover change history, though it doesn't explicitly name the alternatives.

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?

"Explains sudden performance shifts" implies a usage context for diagnosing anomalies, which is helpful. However, it gives no explicit when-to-use/when-not guidance or named alternatives, leaving the agent to infer when to reach for this versus ads_account_audit or ads_query.

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.