Skip to main content
Glama

ADS Beast

audit_performance_coach

Read-only

A prioritised optimisation plan for a client's last 7 days from four specialist reviews (media buying, budget, audience, creative), with a confidence level per item. Recommendations only. Takes up to a minute. 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_performance_coach"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly=true, destructive=false, openWorld=true, so the description's real contribution is operational: a fixed 7-day lookback, a per-item confidence level, and an explicit latency and cost note ('Takes up to a minute. AI: 1 AI request'). That latency/cost disclosure is exactly the kind of context annotations cannot carry. It omits whether results are cached or how many items typically return.

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 sentences, front-loaded with what the tool produces before the operational caveats. The trailing 'AI: 1 AI request.' is terse to the point of being cryptic, but it is at least placed last where it does no harm. No padding.

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 carries the burden of describing the return value and does so adequately: prioritised items, four review domains, confidence levels. Given a one-parameter, no-nested-object tool, the remaining omissions (result format, item count, caching) are minor.

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 0% for the single integer client_id, leaving the description to compensate. It does convey that the input scopes to one client and that the period is fixed at the last 7 days (no date parameter to supply), which is genuinely useful. It does not clarify client_id format or origin, so it only partially closes the gap.

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 concrete deliverable — a prioritised optimisation plan drawn from four named specialist reviews (media buying, budget, audience, creative) with per-item confidence. This distinguishes it from the many single-domain audit_* siblings without having to name them. The verb is implied rather than explicit ('plan ... from four reviews'), which keeps it just short of a 5.

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?

'Recommendations only' usefully signals an advisory output rather than applied changes, and the four-domain framing implies this is the broad coaching option versus narrower single-area audits. However, it never states when to pick this over audit_account, audit_campaign_health, or audit_wasted_spend, nor any prerequisites.

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.