Skip to main content
Glama

SpendCanary free Google Ads tools

Landing page checker

check_landing_page
Read-onlyIdempotent

Loads a public landing page on a phone and a computer and checks speed, redirects, a way to call, book or buy, and the Google tag. Limited to 5 checks an hour.

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": {
      "url": "<url>"
    },
    "name": "check_landing_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe public web address an ad sends people to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description adds real value by disclosing that it fetches the page twice with phone and desktop emulation and by stating a hard throughput limit of 5 checks per hour. It stops short of describing failure behavior or how results 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?

Two compact sentences with zero filler; the core action and the enumerated checks come first and the rate limit is placed as a trailing constraint.

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?

For a one-parameter read-only tool with full annotation coverage, the description tells the agent what is inspected and what throttling applies. The only soft spot is that no output schema exists and the description does not say what the check result looks like.

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% and the single 'url' parameter is fully documented in the schema, so the description only reinforces the 'public' accessibility constraint rather than adding new syntax or format detail. Baseline 3 applies since the schema carries the 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?

Uses a concrete verb+resource ('Loads a public landing page') and enumerates exactly what is verified: speed, redirects, a call/book/buy path, and the Google tag. It is clearly distinct from the analytics-style siblings, 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 Guidelines3/5

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

Usage is only implied: the tool is for evaluating the public destination URL of an ad. There is no statement of when to prefer this over the other listed tools, nor any prerequisites such as the page needing to be publicly reachable without login (that constraint is only hinted at by the word 'public' in the schema).

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.