Skip to main content
Glama

BRAINIAC Technical SEO Audits

Audit canonical tags in a crawl export

seo-technical_canonical-audit
Read-onlyIdempotent

Find missing, multiple, chained, redirecting and noindex canonical targets inside a caller-supplied crawl export. Price $0.03 USDC. POST /api/v1/seo-technical/canonical-audit. 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": {
      "pages": "<pages>"
    },
    "name": "seo-technical_canonical-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
pagesYespages, array. Required.

Output Schema

NameRequiredDescriptionDefault
issuesNoissues. Array.
sourcesNosources. Array.
summaryNosummary. Object.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the price ($0.03 USDC), the transport (POST /api/v1/seo-technical/canonical-audit), and the critical failure mode: an unpaid call returns x402 payment terms and does not execute. That payment-gating behavior is exactly the kind of operational fact the readOnly/idempotent hints cannot convey.

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 short sentences with zero filler: purpose first, then cost, then endpoint and payment behavior. Every clause earns its place and the most decision-relevant content (what it finds) is front-loaded.

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 rich annotations, a fully documented schema, and an output schema to describe results, the description needs only purpose plus operational facts, and it supplies both including the payment gate. The only minor omission is any hint about the shape of the report, which the output schema already covers.

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% and there is only one top-level parameter, so the schema already carries the full burden of documenting 'pages' and its nested fields. The description adds only the framing that the export is caller-supplied, not any new meaning about the parameter's shape or constraints.

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 ('Find ... canonical targets') and enumerates the exact defect classes it detects (missing, multiple, chained, redirecting, noindex). The canonical focus separates it from siblings like seo-technical_redirect-chain-analyze without needing to name them.

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?

The phrase 'inside a caller-supplied crawl export' implies the prerequisite (you must already have crawl data), which is the only usage signal. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative tool for related checks, so guidance is only implied.

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