Skip to main content
Glama

QuiroAds Clinic Marketing Tools

Scan health ad copy for risky phrases

scan_health_ad_copy
Read-onlyIdempotent

Scans the text of a health clinic's ad, post or landing page (up to 4,000 characters) for phrases that Meta and Google ad policies and the health-advertising rules of Spain, the UK, the US and Australia restrict: testimonials and reviews, promises of a cure, a guarantee or a result, superlatives, questions or statements about the reader's condition (Meta), before-and-after, deadlines and fear, and titles such as Dr. Each finding quotes the phrase with its rule, source link, certainty, severity and a safer pattern, and the result lists what a phrase scan cannot judge (images, the landing page, evidence, registration, offer terms). It is a first pass, not a review: it never says whether an ad can be published. Leave out patient names.

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": {
      "text": "<text>",
      "language": "<language>"
    },
    "name": "scan_health_ad_copy"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe ad text, post or landing page copy to scan (up to 4,000 characters). Leave out patient names.
countryNoThe clinic's country, for its health-advertising law: es Spain (with the EU rules), uk, us or au. Without it only the platform rules are scanned.
languageYesLanguage of the answer: es or en. The scan reads both languages either way.
platformNoWhere the ad runs. Without it both platforms' rules are scanned.

Output Schema

NameRequiredDescriptionDefault
noteYes
countsYesFlagged phrases by severity, those not listed included
footerYes
countryYesThe country whose rules were scanned; null: only the platforms' rules
findingsYesMost serious first, then in the order of the text; at most 40
languageYes
platformYesThe platform whose rules were scanned; null: Meta's and Google's
not_checkedYesWhat this scan cannot see
rules_checkedYes
checked_patternsYesHow many of the phrase patterns had a rule in scope
findings_not_shownYesFlagged phrases beyond the 40 listed

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description adds substantial original detail: the shape of each finding (quote, rule, source link, certainty, severity, safer pattern) and an explicit list of what the scan cannot judge (images, landing page, evidence, registration, offer terms). The self-limiting 'first pass, not a review' framing is exactly the kind of behavioral disclosure annotations cannot carry.

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?

Front-loaded with purpose and scope, then limitations, with no filler sentences. It is dense to the point of one very long colon-delimited sentence listing restricted phrase categories, which slightly taxes readability but every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description need not explain return values, and it still summarizes finding structure. Together with rich annotations and full schema coverage, the description covers scope, input hygiene, legal jurisdictions and explicit non-capabilities — nothing an agent needs to call it correctly is missing.

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%, so all four parameters are already fully documented, and the description mostly echoes schema content ('up to 4,000 characters', 'Leave out patient names'). The one genuinely additive hint is that the scan reads both Spanish and English regardless of the answer language, but country/platform fallback behavior is left to the schema text.

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?

States a specific verb (scans) plus a precise resource (health clinic ad/post/landing-page text) and enumerates the exact rule families it checks (Meta/Google policies, ES/UK/US/AU health-advertising law). The scope is narrow enough that an agent can instantly distinguish it from the sibling calculators and playbook tools, none of which analyze copy.

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?

Gives a clear usage boundary in both directions of the sentence 'It is a first pass, not a review: it never says whether an ad can be published,' plus an input constraint ('Leave out patient names'). It lacks any explicit pointer to an alternative tool or a stated trigger scenario, so an agent gets clear context but no named routing alternatives.

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.

Resources