Skip to main content
Glama

BRAINIAC Technical SEO Audits

Build or validate a Google disavow file

seo-technical_disavow-file-build
Read-onlyIdempotent

Validate domain: and URL entries, dedupe, and emit a Google Search Console disavow .txt within documented limits. Price $0.02 USDC. POST /api/v1/seo-technical/disavow-file-build. 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_disavow-file-build"
  }
}

Input Schema

NameRequiredDescriptionDefault
entriesNoentries, array. Required.
existingFileNoexistingFile, value. Optional.

Output Schema

NameRequiredDescriptionDefault
fileNofile. String.
bytesNobytes. Number.
linesNolines. Number.
errorsNoerrors. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.
removedDuplicatesNoremovedDuplicates. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/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 bar is lower, yet the description adds real behavior beyond them: a $0.02 USDC price, the concrete POST endpoint, and the fact that an unpaid call returns payment terms and does not execute. That payment-gating detail is exactly the kind of trait annotations cannot express.

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 with the core action front-loaded, followed by price, endpoint, and payment-failure behavior. The repetition of the endpoint path is mildly redundant with the tool name, but everything present is operational information rather than filler.

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 the two-input surface is small and well covered by the payment and entry-format notes. The one gap is the phrase 'within documented limits', which alludes to disavow size/count caps without stating them, leaving the agent to discover the constraints at call time.

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 own parameter text is generic ('entries, array. Required.'), so the description's mention of 'domain:' and URL entry forms and the dedupe step adds genuine meaning about what belongs in 'entries'. The optional 'existingFile' input is still not explained in the description, which keeps this below 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?

The description gives concrete verbs and a concrete artifact: validate 'domain:' and URL entries, dedupe, and emit a Google Search Console disavow .txt. The output format is named precisely, so an agent can distinguish this from sibling validators such as hreflang-validate or robots-txt-test without inspecting the schema.

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?

Usage is only implied by the description of what the tool produces; there is no explicit statement of when to choose this over sibling technical audits, nor a when-not condition. The x402 payment note at least tells the agent an unpaid call yields terms instead of a result, which is actionable context.

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