Skip to main content
Glama

ADS Beast

audit_campaign_quality

Read-only

Reads every running Google and Meta campaign of a client from the platform and checks geo, conversions against the bid strategy, moderation, landing pages and search assets.

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

Input Schema

NameRequiredDescriptionDefault
client_idYes

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, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds value by clarifying that data is pulled live from the ad platforms ('from the platform'), which explains the open-world trait, and by scoping to running campaigns. It does not disclose latency, rate limits, or whether partial platform failures degrade results.

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 with the verb, scope and checked dimensions in that order; no filler. The long checklist tail is dense but each item carries distinct meaning, so little is wasted.

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 would ideally say what the audit returns (per-campaign findings, pass/fail verdicts, severity). It also doesn't differentiate this audit from the many sibling audit tools, leaving an agent to guess which entry point to use. Adequate for a one-parameter read tool, but with clear gaps.

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?

There is only one parameter and the schema gives it zero description coverage, but the phrase 'of a client' ties the sole client_id argument to the audited entity clearly enough for an agent to supply it correctly. No format or ID-source detail is added, so it stops short of full compensation.

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 uses a specific verb set ('Reads ... and checks') on a defined resource ('every running Google and Meta campaign of a client') and enumerates the audit dimensions (geo, conversions vs bid strategy, moderation, landing pages, search assets). An agent can tell this is a live cross-platform campaign audit, though it never names how it differs from close siblings such as audit_campaign_health or audit_google_ads.

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 only implied: the phrase 'every running ... campaign' implicitly scopes applicability to live campaigns rather than drafts or paused ones, which is useful. However, there is no explicit when-to-use statement, no exclusion for paused/draft campaigns, and no reference to alternatives even though several audit siblings exist.

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.