Skip to main content
Glama

ADS Beast

audit_meta_ads

Read-only

Full Meta Ads audit for a client: funnel structure, audiences, creatives, pixel health, conversion events, audience fatigue and Advantage+ setup. 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_meta_ads"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the audit scope and a useful cost signal ("AI: 1 AI request"), but says nothing about runtime, output form, or whether the audit is cached/repeatable.

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?

Two short sentences, front-loaded with the resource and scope. The trailing "AI: 1 AI request" is a fragment whose meaning is only loosely clear, but it is brief enough not to bloat the definition.

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 should signal what the audit returns, and it only lists topics rather than deliverables. The unmentioned required client_id also leaves a gap, though the annotations carry the safety profile adequately.

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 single required parameter client_id has 0% schema description coverage and the description does not mention it at all. An agent gets no guidance on what identifier format is expected or whether the client must already be connected.

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?

Names a specific verb and resource ("Full Meta Ads audit for a client") and enumerates the audit dimensions covered, which separates it from narrower siblings like audit_campaign_health or audit_tracking. It never names a sibling explicitly, so differentiation is implied rather than stated.

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 word "Full" implies this is the comprehensive option versus the more targeted audit_* tools, but there is no explicit when-to-use statement, no prerequisites, and no named alternative. The agent must infer the selection rule from the adjective alone.

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.