Skip to main content
Glama

BRAINIAC Technical SEO Audits

Internal PageRank and click depth

seo-technical_internal-link-graph
Read-onlyIdempotent

Compute PageRank, in/out degree and BFS click depth from caller-supplied internal link edges. Price $0.04 USDC. POST /api/v1/seo-technical/internal-link-graph. 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>",
      "start": "<start>"
    },
    "name": "seo-technical_internal-link-graph"
  }
}

Input Schema

NameRequiredDescriptionDefault
edgesYesedges, array. Required.
startYesstart, string, length 1 to 4096. Required.
dampingNodamping, number. Required.
excludeNofollowNoexcludeNofollow, boolean. Required.

Output Schema

NameRequiredDescriptionDefault
nodesNonodes. Array.
sourcesNosources. Array.
componentsNocomponents. Number.
iterationsNoiterations. Number.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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-obvious behavior: a $0.04 USDC price, the endpoint, and that an unpaid call returns x402 payment terms without executing. It does not describe output shape or any limits, but the output schema covers returns.

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 what is computed, followed by cost and transport details. Nothing is padded, though the raw endpoint path is the least essential element and the telemetry-style phrasing is slightly clipped.

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?

With 4 parameters at full schema coverage, an output schema, and annotations covering safety, the description supplies the remaining critical facts an agent needs: that it is paid, that payment failure means no execution, and that it works on supplied edges rather than crawling. Only per-parameter semantics and output ordering remain unaddressed, and those are low-risk here.

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 the baseline is 3. The description hints at the edges input and the start-dependent BFS depth, but adds no meaning for damping, excludeNofollow, or the nofollow flag semantics beyond what the schema already states.

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 specific verbs and outputs (compute PageRank, in/out degree, BFS click depth) and names the input source (caller-supplied internal link edges), which implicitly separates it from crawl-based siblings like crawl-depth-analyze. It does not explicitly name an alternative, so it stops short of full sibling differentiation.

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?

'From caller-supplied internal link edges' implies the precondition that the caller already has a link graph and is not asking this tool to crawl, which is useful implied context. There is no explicit when-to-use/when-not guidance or named alternative among the many seo-technical siblings.

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