Skip to main content
Glama

ADS Beast

audit_google_ads

Read-only

Full Google Ads audit for a client: structure, keywords, responsive search ads, extensions, bidding, conversions and Quality Score problems, with a 0-100 score and recommendations. AI: 1 AI request.

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": {
      "client_id": "<client_id>"
    },
    "name": "audit_google_ads"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNoquick or full.full
client_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so safety is covered. The description adds genuine value beyond that: it discloses the scope of checks performed, the output shape (0-100 score plus recommendations), and a cost signal ('AI: 1 AI request'). It stops short of explaining latency, data freshness, or what happens on accounts with limited data.

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?

A single front-loaded sentence lists scope and deliverable, followed by a terse cost note. Nothing is padded, though the 'AI: 1 AI request.' fragment is telegraphic and could be phrased more clearly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 does cover return values (score plus recommendations) and cost, which is the important part for a read-only audit. The gaps are on the input side: neither the depth modes nor client_id are explained, so an agent must guess at the effect of its parameters.

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 coverage is only 50% and the existing depth description is a tautology ('quick or full.'). The description says nothing about what 'quick' versus 'full' actually changes, and client_id is completely undocumented in either schema or description. Meaning beyond the schema is essentially absent.

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 verb and resource ('Full Google Ads audit for a client') and enumerates the areas checked (structure, keywords, RSAs, extensions, bidding, conversions, Quality Score) plus the deliverable (0-100 score and recommendations). It is clear what the tool does, but it does not distinguish itself from the many sibling audit tools (audit_account, audit_campaign_health, audit_campaign_quality, audit_wasted_spend) that plausibly overlap.

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?

The word 'Full' and the depth enum hint that this is the comprehensive audit versus narrower one, so usage is implied. However, there is no explicit statement of when to choose this over the other audit tools and no preconditions or exclusions mentioned.

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.