Skip to main content
Glama

BRAINIAC Technical SEO Audits

Click-depth distribution from link edges

seo-technical_crawl-depth-analyze
Read-onlyIdempotent

Multi-source BFS depth distribution with too-deep important URLs and unreachable nodes from caller edges. Price $0.03 USDC. POST /api/v1/seo-technical/crawl-depth-analyze. An unpaid call returns the x402 payment terms and does not run.

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": {
      "edges": "<edges>",
      "startUrls": "<startUrls>"
    },
    "name": "seo-technical_crawl-depth-analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
edgesYesedges, array. Required.
maxDepthNomaxDepth, integer, from 0 to 100. Required.
importantNoimportant, array. Required.
startUrlsYesstartUrls, array. Required.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
tooDeepNotooDeep. Array.
limitationsNolimitations. Array.
unreachableNounreachable. Array.
distributionNodistribution. Object.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely new context the annotations lack: the $0.03 USDC price, the HTTP endpoint, and that an unpaid call returns x402 payment terms without executing. It does not say anything about result size, limits, or what happens with an empty edge list.

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 core computation before billing and endpoint details. Dense and jargon-heavy ('Multi-source BFS depth distribution') but every sentence carries information; nothing is padding.

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 explained, and the payment path is unusually well covered for an agent that must decide whether a call will actually execute. What remains thin is operational detail about how inputs are interpreted (source set, depth semantics), which matters for a graph tool but is not critical.

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%, so every parameter is already documented in the schema; baseline 3 applies. The description only obliquely adds meaning - 'caller edges' hints that edges/startUrls must be assembled by the agent, and 'too-deep important URLs' hints at the important parameter - but it never explains what maxDepth controls or how the sources interact.

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 description names a specific algorithm and resource: 'Multi-source BFS depth distribution ... from caller edges', plus the two notable outputs (too-deep important URLs and unreachable nodes). An agent knows this computes click-depth metrics from a supplied link graph. It does not explicitly contrast with the closest sibling, orphan-page-detect, but the substance is clear.

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 statement of when to use this versus alternatives such as orphan-page-detect or internal-link-graph, and no preconditions beyond the implicit requirement to supply edges and startUrls. Usage is only inferable from the phrase 'from caller edges', which tells the agent it must build the graph itself but nothing about tool selection.

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