Skip to main content
Glama

ADS Beast

audit_ad_disapprovals

Read-only

Ads the platforms rejected, with the reason and the policy code.

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

Input Schema

NameRequiredDescriptionDefault
statusNoopen (default), acknowledged, fixed, wontfix or all.
platformNogoogle, meta, tiktok, linkedin or microsoft.
client_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the meaningful behavioral detail that results include a rejection reason and policy code, but says nothing about volume, ordering, or whether platforms are queried live.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no wasted clauses, which is good, but the subject is a sentence fragment ('Ads the platforms rejected') rather than a clear statement of action, which slightly hurts readability.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter filtered list tool with no output schema, the description should say what the filters do and roughly what comes back. It mentions the return payload's fields but leaves the filtering behavior and the undocumented client_id entirely to the 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?

The description mentions no parameters at all, while schema coverage is only 67% — client_id has no description anywhere, and platform/status semantics (multi-value? default?) are only lightly covered. The description does not compensate for that gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase 'Ads the platforms rejected' is a fragment but does convey that this returns disapproved ads, and it adds that each result carries a reason and a policy code. It does not distinguish itself from sibling audit tools such as audit_google_ads or audit_meta_ads, which could plausibly surface similar data.

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 guidance on when to call this versus the many audit_* siblings, no mention of prerequisites, and no note on how the status default behaves in practice. The only usage hint is the schema's 'open (default)', which lives outside the description.

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.