Skip to main content
Glama

ADS Beast

audit_account

Read-only

AI audit of a client's ad account on one platform or all of them. Takes 10-30 seconds. 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_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformNogoogle, meta, tiktok, linkedin or microsoft.all
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 and openWorldHint=true, so the safety profile is covered. The description adds genuinely non-derivable operational context: an expected runtime of 10-30 seconds and a cost of '1 AI request', which matters for planning and quota budgeting. It stops short of describing what the audit actually evaluates or returns.

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?

Three short, front-loaded sentences with no filler; purpose comes first, then latency, then cost. 'AI: 1 AI request' is terse to the point of being slightly cryptic in phrasing, but it earns its place as a quota signal.

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?

For a read-only audit tool with no output schema, the description should indicate what the audit covers or roughly what comes back; it says nothing about the report contents. Latency and cost are covered, but an agent still cannot predict the result shape or decide between this and the narrower audit siblings.

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 50%: platform already lists its accepted values in the schema, and the description only restates its scope ('one platform or all of them'). client_id is undocumented in both the schema and the description, so the agent gets no signal about where the ID comes from or how to obtain it. Baseline 3 is appropriate given partial coverage.

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 gives a specific verb and resource ('AI audit of a client's ad account') plus scope ('one platform or all of them'), so an agent knows exactly what is produced. It does not differentiate itself from the many sibling audit tools (audit_google_ads, audit_meta_ads, audit_campaign_health, etc.), so an agent cannot tell from the text alone whether this is the generic roll-up or a duplicate of a platform-specific audit.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative. The phrase 'on one platform or all of them' hints at the platform parameter's role, but nothing tells the agent whether to prefer this over the platform-specific audit siblings or the narrower audits like audit_wasted_spend.

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.