Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_api_seo_xray

Audit a URL’s on-page SEO to identify title, meta, heading, link, and content issues, then use the structured findings to guide page fixes.

Instructions

[Web Intelligence] On-page SEO audit of a URL Measured p50 12 ms, p95 15 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://api.caelaralabs.com.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPage URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the burden alone; it does disclose latency benchmarks (p50 12 ms, p95 15 ms) and the upstream endpoint contacted, which is real behavioral context an agent cannot get from structured fields. However, it never says whether the page is fetched live, what checks are performed, or what the response looks like, so the read-only, no-mutation nature is only implied.

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?

Three short sentences, front-loaded with the purpose, with no filler sentences. The benchmark citation with date and source domain is mildly noisy for a tool-selection decision, but the definition stays compact overall.

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?

For a single-parameter audit tool with no output schema and no annotations, the description should convey what the audit produces (checks performed, scoring, return shape). It instead spends its remaining budget on latency statistics and the API hostname, leaving the agent unable to anticipate results.

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 there is a single required 'url' parameter documented as 'Page URL', so the baseline is 3. The description adds nothing beyond the schema — it does not specify that the URL must be absolute or include a scheme, nor any normalization behavior.

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?

States a specific verb and object: 'On-page SEO audit of a URL', which tells an agent the action and target precisely. It does not distinguish itself from closely related siblings such as caelara_seo_technical_seo_composite or caelara_seo_schema_org_validator, so scope boundaries remain unclear.

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 guidance on when to use this tool rather than the technical SEO composite, schema validator, or geo-readiness tools. The only contextual cue is the '[Web Intelligence]' tag, which does not indicate selection conditions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools