Skip to main content
Glama

BRAINIAC Technical SEO Audits

Detect orphan and unsitemap pages

seo-technical_orphan-page-detect
Read-onlyIdempotent

Compare normalised sitemap, crawl and analytics URL sets to find orphans, missing sitemap entries and no-traffic pages. Price $0.02 USDC. POST /api/v1/seo-technical/orphan-page-detect. An unpaid call returns the x402 payment terms and does not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "seo-technical_orphan-page-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
crawledUrlsNocrawledUrls, array. Required.
sitemapUrlsNositemapUrls, array. Required.
stripParamsNostripParams, array. Required.
analyticsUrlsNoanalyticsUrls, array. Required.
ignoreTrailingSlashNoignoreTrailingSlash, boolean. Required.

Output Schema

NameRequiredDescriptionDefault
orphansNoorphans. Array.
sourcesNosources. Array.
noTrafficNonoTraffic. Array.
limitationsNolimitations. Array.
notInSitemapNonotInSitemap. Array.
normalisationNonormalisation. Object.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-redundant behavior: a $0.02 USDC cost, the POST endpoint, and that an unpaid call returns x402 payment terms without executing. It does not mention rate limits or set-size limits, which keeps it below a 5.

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 comparison before cost and transport details. Every sentence carries operative information an agent needs before calling.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. Payment mechanics and input requirements are present; only minor gaps remain, such as array size expectations and how empty sets are handled.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is nominally 100%, but the schema's parameter descriptions are generic restatements ('crawledUrls, array. Required.'). The description compensates by tying sitemapUrls, crawledUrls and analyticsUrls to concrete roles and by implying normalization, which is what stripParams and ignoreTrailingSlash control. It still does not explain default behavior of those two flags, so it is not a 5.

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: compare normalised sitemap, crawl and analytics URL sets to find orphans, missing sitemap entries and no-traffic pages. That output triad clearly separates it from siblings like xml-sitemap-validate and url-parameter-audit, which do not cross-compare URL sets.

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?

By naming the three input sets it implicitly tells the agent when the tool applies (you need sitemap, crawl and analytics data). However it never states prerequisites explicitly, nor when to prefer a sibling such as xml-sitemap-validate, so guidance is implied rather than stated.

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