Skip to main content
Glama

Ad Spec Guard

check_ad_policy_preflight

Read-only

Scan ad copy for the two patterns behind most rejections: a business category the platform prohibits or gates behind certification, and a claim the platform treats as unverifiable. Returns each match with the governing policy page. This is a pattern pre-check, not an approval; only the platform's review decides whether an ad runs.

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": {
      "platform": "<platform>",
      "text": "<text>"
    },
    "name": "check_ad_policy_preflight"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe ad copy to check.
platformYesAd platform. Known keys: apple, google, linkedin, meta, microsoft, reddit, telegram, tiktok.
verticalNoOptional business category, for example 'dental clinic'.
landing_urlNoOptional landing page URL, checked alongside the copy.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already cover readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile is known. The description adds genuinely useful context beyond that: it discloses the limited detection scope (two patterns) and states that results are advisory, not an approval decision. It says nothing about match format detail, coverage gaps per platform, or what an empty result implies.

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?

Three tight sentences, front-loaded with what it scans and what it returns, followed by the essential caveat. Every sentence carries information an agent needs and none restates the tool name.

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 takes on the burden of explaining results and does so at a useful level: each match comes back with its governing policy page. Combined with full schema coverage and read-only annotations, an agent has enough to call it correctly, though edge behavior such as no-match results is left unstated.

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 100%, so every parameter, including the known platform keys and the optional vertical and landing_url, is already documented in the schema. The description only reinforces that ad copy is the subject of the scan and adds no format, validation, or interaction semantics (for example, how landing_url is combined with the copy). Baseline 3 is appropriate.

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 gives a specific verb and resource ('Scan ad copy') and narrows the scope precisely to two failure patterns: prohibited/gated business categories and unverifiable claims. It does not explicitly distinguish itself from the similarly named sibling validate_ad_copy, so the reader must infer the split.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly frames the use case ('pattern pre-check, not an approval') and states the limit of its authority, which tells an agent when to rely on it and when a platform review is still required. It stops short of naming an alternative tool or exclusion conditions explicitly.

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.