Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

list_site_audit_issues

Retrieve technical SEO issues from the latest site crawl, ordered by severity. Filter by severity or category to prioritize fixes and see how many pages each issue affects.

Instructions

The technical issues detected by the latest crawl, most severe first — each with issue_code (pass it to list_site_audit_issue_pages), title, severity, category, pages_affected (with prev and delta), how_to_fix guidance and priority. Filter by severity and/or category; cursor-paginated (limit max 200).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does unusually well: it discloses result ordering (most severe first), pagination mechanics (cursor-based, limit max 200), and that data is scoped to the latest crawl only. It does not state read-only semantics, rate limits, or what happens with an expired cursor, leaving some behavioral gaps.

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?

One front-loaded sentence establishes the resource and ordering, then the returned-field inventory and the filter/pagination contract. Every clause carries information the agent needs, especially since no output schema exists.

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?

With no output schema and no annotations, the description compensates by enumerating returned fields (issue_code, title, severity, category, pages_affected with prev/delta, how_to_fix, priority) and by documenting pagination and sort order. It is nearly complete; the only gap is not clarifying whether resolved/passed checks are excluded.

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?

The schema is an open object with no documented properties, so the description must supply parameter meaning — it does by naming severity and category as filters and noting cursor/limit (max 200). It does not enumerate allowed severity values or the cursor token format, so an agent still has to guess accepted inputs.

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 resource (technical issues detected by the latest crawl), its ordering (most severe first), and its scope limit (latest crawl only), which separates it from historical/cross-crawl siblings like compare_site_audit_crawls. It also names the follow-up sibling and the exact key to hand it (issue_code -> list_site_audit_issue_pages).

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 clear usage context: this is the entry point to enumerate issues, filterable by severity and/or category, with an explicit next step for per-page detail. It stops short of stating when NOT to use it — e.g. versus get_site_audit_summary for aggregate counts or compare_site_audit_crawls for trend analysis.

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