Skip to main content
Glama

RootMention SEO

run_seo_audit

Read-only

Audit a public homepage and up to two discovered product/collection pages. Requires user authorization. Respects robots.txt; returns findings inline without saving a report or sales lead. Maximum 35 seconds, three attempts per IP per hour, 30 shared audit attempts per hour.

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": {
      "website": "<website>",
      "authorized": "<authorized>"
    },
    "name": "run_seo_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
websiteYes
authorizedYesTrue only when the user confirms they own or are authorized to audit the website.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, openWorld, non-idempotent, non-destructive), and the description adds substantial context beyond them: robots.txt compliance, a 35-second ceiling, dual rate limits, and the fact that no report or sales lead is persisted. These are exactly the operational constraints an agent needs before invoking a long-running, externally visible crawl.

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?

Four tight sentences, front-loaded with what is audited before the constraints. No filler, and each sentence carries a distinct operational fact.

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?

No output schema exists, so the description correctly states that findings are returned inline and nothing is saved. Combined with the authorization prerequisite, robots.txt stance, timeout, and rate limits, an agent has everything needed to call it correctly.

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?

With only 50% schema coverage, the description partially compensates by constraining the target to a "public homepage" and by reinforcing the authorization requirement that maps to the authorized boolean. It does not elaborate on the website URI format or length bound, which the schema already declares.

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 with explicit scope: auditing a public homepage plus up to two discovered product/collection pages. That scope alone separates it from calculate_seo_break_even and get_services 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear prerequisite ("Requires user authorization") and operational context via the per-IP and shared hourly attempt caps, which tells the agent when the tool is realistically callable. It stops short of naming alternatives or stating explicit when-not-to-use conditions.

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.