Skip to main content
Glama

MetricPort

Account audit

ads_account_audit
Read-onlyIdempotent

One call that runs the key checks: campaign totals vs. previous period, wasted spend share, impression share lost to budget/rank, low quality score cost, budget pacing and open Google recommendations. Produces a prioritized findings list.

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_account_audit"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered structurally. The description adds genuinely new behavioral context: this is a multi-check aggregation performed in a single call, and it returns a prioritized findings list rather than raw metrics. It still omits any note about latency/cost of fanning out across many checks or auth requirements.

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?

Two tight sentences, front-loaded with the operation and then the output. The enumeration of checks is dense but each item earns its place by telling the agent what will be computed, and there is no filler or restatement of the name.

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 no output schema, the description correctly takes on the job of stating the return shape ('prioritized findings list'). For a read-only two-parameter audit tool this is nearly complete; the only real gap is the undefined 'days' lookback window, which the agent must discover from the schema alone.

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

Parameters2/5

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

Schema description coverage is only 50%: 'property' is documented in the schema, but 'days' (min 7, max 90, default 30) has no description. The description never mentions either parameter or the lookback window, so it fails to compensate for the coverage gap on a parameter that materially changes every computed comparison.

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?

The description names a specific composite operation and enumerates the exact checks it runs (campaign totals vs. prior period, wasted spend share, impression share lost to budget/rank, low quality score cost, budget pacing, open recommendations), so an agent can tell it is an aggregate audit rather than a single-metric tool. It does not explicitly state that it supersedes the individual sibling tools (ads_wasted_spend, ads_budget_pacing, ads_quality_score_audit, ads_recommendations), leaving that distinction to inference.

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?

"One call that runs the key checks" implies this is the consolidated overview option versus running the individual sibling tools separately, which is useful implied guidance. However, there is no explicit when-to-use statement, no exclusions (e.g. not for deep dives on one metric), and no mention of prerequisites such as obtaining the customer id from list_properties.

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.