Skip to main content
Glama

ADS Beast

seo_technical_audit

Read-only

Core Web Vitals, crawlability, indexability, structured data, redirects, canonicals, mobile, HTTPS, robots.txt and sitemap. AI: 1 AI request.

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": {
      "url": "<url>"
    },
    "name": "seo_technical_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYeshttps:// page URL.
depthNoquick, standard or deep.standard
client_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is known. The description adds one genuinely non-obvious behavioral fact — 'AI: 1 AI request' — signalling a metered cost per call. It says nothing about runtime, whether the page is fetched live, or the shape/scope of the result.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very short with no filler, and the cost note is placed last where it is easy to miss. However, it is an unpunctuated fragment with no lead sentence telling the agent what the tool returns, so brevity comes at the expense of structure rather than from efficiency.

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

Completeness2/5

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

For a broad, multi-check audit with no output schema, the description gives no indication of what the caller receives — a score, a list of failed checks, per-category findings — nor how the depth setting affects that output. An agent can invoke it but cannot anticipate or plan around the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%; url and depth have schema descriptions, but client_id has none, and the description contributes no parameter meaning at all. Critically, the depth enum values quick/standard/deep are never explained — what changes in coverage, cost or runtime between them is left entirely unstated despite being the main decision the caller makes.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a noun-phrase feature list (Core Web Vitals, crawlability, indexability, redirects, canonicals, mobile, HTTPS, robots.txt, sitemap) with no verb stating what the tool actually does — analyze, score, or report. The scope is nonetheless clear enough to separate it from siblings like seo_content_quality_audit or seo_domain_authority_audit, since those cover different areas.

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 when-to-use guidance, no prerequisite (e.g. that the URL must be live and publicly reachable), and no mention of any alternative audit tool or when to pick a narrower audit instead. The agent must infer usage entirely from the topic list and the sibling names.

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.