Skip to main content
Glama

Caelara Labs Web Intelligence

seo_xray

On-page SEO audit of a URL

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

Input Schema

NameRequiredDescriptionDefault
urlYesPage URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden, yet it says nothing about whether the audit fetches the live page, how long it takes, whether it is read-only/rate-limited, or what 'audit' covers. Only the qualifier 'on-page' hints at scope (page content rather than backlinks), which is a small amount of real information against a large gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is a single six-word noun phrase with zero wasted words, but it is under-specified rather than genuinely concise, and there is no structure to front-load.

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

Completeness2/5

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

With no annotations and no output schema, the description is the only source of behavioral information, and it does not say what the audit returns, how findings are reported, or what an agent should do with the result. For a tool whose whole value is its output structure, this is a substantial gap.

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?

With one parameter and 100% schema description coverage, the schema already defines 'url' as 'Page URL'. The description's 'of a URL' merely restates that, adding no format, protocol, or scope constraints; baseline 3 applies when the schema does the work.

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 phrase 'On-page SEO audit of a URL' names a specific verb (audit) and a specific resource (a single page's on-page SEO), which clearly distinguishes it from sibling utilities like url_to_markdown or sitemap_crawler. It stops short of 5 because it never contrasts itself with those siblings explicitly, leaving the agent to infer the boundary.

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 guidance, no prerequisites, and no mention of alternatives. An agent must guess whether this is for a single page vs. a whole site, or whether it competes with url_to_markdown for fetching a page.

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