Skip to main content
Glama

ADS Beast

chatgpt_ads_policy_check

Read-only

Whether ChatGPT Ads policy admits this business and whether the texts fit the limits (title 50, body 100).

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

Input Schema

NameRequiredDescriptionDefault
urlNoLanding page.
bodyNoAd text.
textNoThe business, offer or campaign theme.
titleNoAd title.
client_idNo
context_hintsNoConversation themes, not keywords.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 concrete behavioral substance in the form of the enforced limits (title 50, body 100), but says nothing about what a failing result looks like, whether it validates all fields at once, or how policy decisions are reported.

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?

A single front-loaded sentence that states both checks and embeds the limits inline with no filler. Every clause carries information an agent needs.

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 six-parameter, open-world tool with no output schema and no required parameters, the description should explain what the response contains (per-field pass/fail? policy reasons?) and how the inputs are used together. It covers the core check well but leaves the return contract and the role of context_hints/client_id entirely to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 83%, so the baseline is 3; the description earns above baseline by attaching hard constraints to title and body (50 and 100 characters) that the schema does not state. It leaves url, text, client_id and context_hints unexplained, but the added constraint semantics are genuinely useful.

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 specific resource (ChatGPT Ads policy) and the two things checked: business admissibility and text length limits. That is far more precise than the tool name alone and distinguishes it from drafting/publishing siblings like chatgpt_ads_draft_generate or prepare_chatgpt_ads_publish, though it never explicitly contrasts itself with them.

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 when-to-use statement, no prerequisites (e.g. run before drafting or publishing), and no named alternative. An agent can infer it is a pre-flight compliance gate, but nothing in the text confirms that or says when it should be skipped.

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.