Skip to main content
Glama

ADS Beast

audit_wasted_spend

Read-only

Campaigns that burn budget: spend with zero conversions, CPA above target, no clicks. Returns the amounts lost, in the account currency.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "audit_wasted_spend"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back days.
client_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/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 useful context by stating the return payload ('amounts lost, in the account currency'). It does not disclose auth needs, whether the CPA target is configurable, or the granularity of the results.

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 short sentences, with the detection criteria front-loaded and the return-value note following. Every clause carries information; there is no filler.

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 simple two-parameter read-only tool with no output schema, the description adequately covers what is found and what is returned. It leaves open how the CPA target is determined, whether results are per campaign or aggregated, and what client_id scopes, which are meaningful gaps given the absent output schema.

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%: 'days' is documented in the schema, but 'client_id' has no description anywhere. The description never mentions either parameter, so it does not compensate for the undocumented client_id or clarify whether the look-back window affects the CPA 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 the resource (campaigns) and the exact detection criteria: zero conversions, CPA above target, no clicks. It is more specific than a generic 'audit' label. It does not explicitly distinguish itself from the many sibling audit_* tools, so it falls 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?

The listed waste criteria implicitly tell an agent when the tool is relevant, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative. It also never says where the 'target' CPA comes from, which an agent would need to know before relying on the results.

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.