Skip to main content
Glama

BRAINIAC Technical SEO Audits

Audit URL parameter explosion

seo-technical_url-parameter-audit
Read-onlyIdempotent

Find parameter usage, tracking params and duplicate-content URL groups from a caller-supplied URL list. Price $0.02 USDC. POST /api/v1/seo-technical/url-parameter-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": {
      "urls": "<urls>"
    },
    "name": "seo-technical_url-parameter-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYesurls, array. Required.
trackingParamsNotrackingParams, array. Required.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
trackingNotracking. Array.
parametersNoparameters. Array.
limitationsNolimitations. Array.
combinationsNocombinations. Array.
duplicateGroupsNoduplicateGroups. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive behavior, so the description only needs to add context — and it does: price ($0.02 USDC), transport (POST /api/v1/...), and the important failure mode that an unpaid call does not execute. Return shape is covered by the output schema, so no further disclosure is required.

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?

Four short, front-loaded sentences covering purpose, price, endpoint, and payment failure mode, with no filler. Minor waste in restating the endpoint path that is already implied by the tool identity, but nothing obscures the core meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, read-only audit with a full output schema and rich annotations, the description supplies everything else an agent needs: what is analyzed, what is returned at a high level, the cost, and the unpaid-call behavior. No material gap remains.

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 both parameters are documented there, so baseline is 3. The description mentions 'tracking params' as an output concept but does not clarify that the caller supplies the tracking-parameter list or note the built-in utm/gclid defaults, leaving schema as the sole source.

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 a specific verb ('Find') and three concrete outputs (parameter usage, tracking params, duplicate-content URL groups) over a defined input (a caller-supplied URL list). It is clearly distinct from sibling audits such as canonical-audit or hreflang-validate, though it does not name an alternative explicitly.

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?

It establishes the key precondition — a paid call, with unpaid calls returning x402 payment terms instead of running — and that input is a caller-supplied list. It gives no guidance on when to prefer this over related audits (e.g., canonical-audit) or on list size/eligibility constraints.

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