Skip to main content
Glama

Black SEO Analyzer

serp_preview

Read-onlyIdempotent

Fetch each URL and report how its title and meta description will look in a search result: character length, pixel width, whether the engine will truncate it, and the Open Graph and Twitter Card fallbacks. Use it when the user asks how a page "looks in Google" or is rewriting titles and descriptions - it is about the snippet, not the page's other SEO problems, which check_page covers. At most 50 URLs per call; does not count against the page budget; limited to 30 calls a minute.

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": {
      "urls": "<urls>"
    },
    "name": "serp_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYesAbsolute URLs to preview. At most 50 per call.
engineNoSearch engine whose truncation rules to apply: "google" (default) or "bing".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (which already declare read-only, idempotent, non-destructive), the description adds operational constraints an agent cannot get elsewhere: a 50-URL cap, a 30-calls-per-minute rate limit, and the notable fact that these calls do not consume the page budget. It also discloses the shape of what comes back (length, pixel width, truncation verdict, social-card fallbacks).

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 sentences, front-loaded with the core action and outputs, then usage routing, then operational limits. Every clause carries information — no restating of the tool name, no filler.

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?

For a read-only preview tool with two simple parameters and no output schema, the description supplies everything needed: what it returns, when to call it, when to call a sibling instead, and the rate/budget constraints. Nothing material 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 both parameters are already documented, including the engine enum values in prose. The description reinforces the 50-URL limit and implies engine-specific truncation rules, but adds no syntax or format detail beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 and resource ("Fetch each URL and report how its title and meta description will look in a search result") and enumerates the exact outputs: character length, pixel width, truncation, and Open Graph/Twitter Card fallbacks. It also explicitly carves out scope against the sibling check_page, so an agent can distinguish the two without reading either schema.

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

Usage Guidelines5/5

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

Gives an explicit trigger ("when the user asks how a page 'looks in Google' or is rewriting titles and descriptions") and an explicit exclusion with the named alternative ("it is about the snippet, not the page's other SEO problems, which check_page covers"). Both when-to-use and when-not-to-use are covered.

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.