Skip to main content
Glama

SpendCanary free Google Ads tools

Ad copy checker

check_ad_copy
Read-onlyIdempotent

Checks Google responsive search ad or Meta ad text against character limits and common rejection reasons (symbols, capitals, repeated text, claims). Returns issues per line: fix (likely rejected or cut off) or look (worth a second look).

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

Input Schema

NameRequiredDescriptionDefault
pathsNoGoogle display path fields (up to 2).
keywordNoThe main keyword or service the ad is for.
platformNogoogle for a responsive search ad, meta for a Facebook or Instagram adgoogle
headlinesNoGoogle: up to 15 headlines. Meta: headlines.
descriptionsNoGoogle: up to 4 descriptions. Meta: descriptions.
primary_textNoMeta primary text variations.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false, idempotentHint and closed-world behavior, so the safety profile needs no restating. The description goes further by classifying returned findings into 'fix' (likely rejected or truncated) versus 'look' (worth a second look), which is meaningful behavioral context absent from the annotations. It stops short of describing limits per platform or how many issues are returned.

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?

Two tight sentences; the validation targets come first and the return-value classification last. Nothing is repeated from the title or schema, and no sentence is filler.

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 correctly steps in to explain the shape of results (issues per line, tagged fix or look). For a six-parameter, zero-required tool it could be slightly more explicit about needing at least one ad-text field and about per-platform character limits, but the essentials for correct invocation are present.

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 description coverage is 100%, and the schema itself maps headlines/descriptions to Google versus Meta usage and caps counts. The description adds only the notion that inputs are ad text validated per line, without clarifying that zero parameters are required or which fields apply to which platform beyond the schema. Baseline 3 is appropriate when the schema carries the load.

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

Purpose5/5

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

Uses a specific verb (checks) with a specific resource (Google responsive search ad or Meta ad text) and names the exact failure classes it validates (character limits, symbols, capitals, repeated text, claims). It is clearly distinguishable from sibling calculators like cpc or roas and from check_landing_page.

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 domain of use is implied by the platform-specific scope, but there is no explicit statement of when to call this versus check_landing_page or before publishing a campaign. No exclusions or preconditions are given, so an agent must infer the trigger from the purpose line 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.