Skip to main content
Glama

ADS Beast

meta_ads_placement_safety_check

Read-only

Shows which ad sets of a client's active Meta campaigns still run on fraud-prone placements and what the safe targeting would be. Read-only.

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": "meta_ads_placement_safety_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_idYes
objectiveNoMeta objective, OUTCOME_LEADS by default.
include_bot_audienceNoAlso plan the bot exclusion audience.

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 and destructiveHint=false, so the trailing 'Read-only' is mostly redundant. The description does add real context beyond the annotations: it scopes results to active campaigns only and discloses that the output includes a proposed safe targeting, which tells the agent this is a planning surface rather than a pure audit. It stops short of describing volume, per-account limits, or pagination.

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 core behavior, with no filler. The only slight waste is the closing 'Read-only,' which restates the readOnlyHint annotation rather than adding information.

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 check tool with no output schema, the description gives an adequate sketch of the return (flagged ad sets plus safe targeting). It is incomplete on the two optional parameters, whose effect on results is undocumented anywhere, and gives no sense of result scope or format. Adequate but with clear gaps.

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 67%, below the high-coverage threshold, so the description needs to compensate and does not. It never mentions client_id, the objective override (defaulting to OUTCOME_LEADS), or the include_bot_audience flag, so the reader learns nothing about how those inputs change the result. Only the schema supplies any parameter meaning.

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 a specific verb and resource: it 'shows which ad sets of a client's active Meta campaigns still run on fraud-prone placements.' It also states the deliverable ('what the safe targeting would be'), so an agent can tell this is a diagnostic/planning read rather than an apply step. It does not explicitly name the apply sibling as the follow-up action, which keeps it from 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?

Use is implied by the framing: this is a check that produces a safe-targeting recommendation, which naturally precedes an apply tool. However, there is no explicit when-to-use or when-not-to-use statement, no mention of prerequisites (does the client need active campaigns?), and no named alternative for the write path.

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.