Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

get_site_audit_page

Retrieve full crawl audit details for a single URL, including status code, indexability and health scores, and each failing check with severity and how to fix it.

Instructions

Full crawl detail for a single URL: status_code, crawl_depth, indexability_score and health_score, category_scores, issue_counts and issues[] — the page's failing checks, each with issue_code, severity, category, the per-page description and how_to_fix.

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": "get_site_audit_page"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and all it discloses is the shape of the returned payload. It says nothing about whether the page must exist in a completed crawl, what happens for a URL not in the audit, whether results are scoped to a project or latest crawl, or whether the call is cheap or expensive.

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?

A single front-loaded sentence with the resource stated first and the payload enumerated after the colon; the field list is dense but each item tells the agent what it will get. No filler or restated title, though the enumeration gets long.

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

Completeness3/5

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

With no output schema and no annotations, the return-field enumeration is genuinely necessary and well done. What is missing is the input contract (how to identify the URL/crawl) and any scope caveats, which leaves an agent unable to confidently invoke it.

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?

The schema declares zero parameters with additionalProperties=true, so the agent gets no structured guidance on how the target URL is supplied — the description likewise never names the input or its format. With 0 params the baseline would be 4, but the missing target-URL contract is a genuine gap for a tool whose entire job is 'a single URL'.

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?

The description gives a specific verb and resource ('Full crawl detail for a single URL') and enumerates exactly what comes back, so it is clearly the per-page counterpart to get_site_audit_summary. It stops short of naming that sibling or explicitly contrasting the scope, so differentiation is inferable rather than stated.

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: 'a single URL' signals drill-down after an aggregate view, and the issue-level payload implies debugging failing checks. There is no explicit when-to-use, when-not-to-use, or routing sentence pointing at get_site_audit_summary or list_site_audit_issue_pages.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools