Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

list_site_audit_issue_pages

Lists the exact URLs affected by a site audit issue using its issue_code, returning each offending page with its per-page value. Turns crawler issues into a concrete fix list.

Instructions

The exact URLs affected by one issue — pass its issue_code and get each offending url with the per-page value. Cursor-paginated (limit max 200). Turns any Crawler issue straight into a concrete fix list.

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_issue_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose the two traits an agent needs: cursor pagination and a limit ceiling of 200. It also reveals the return shape (one record per URL with a per-page value). It omits default page size and any permission/auth requirements, but for an evidently read-only list tool the disclosure is solid.

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?

Three short sentences, each earning its place: scope first, mechanics second, payoff third. Front-loaded with the effective resource definition and no redundant restatement of the tool name.

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?

No output schema exists, and the description compensates by describing the returned fields (url plus per-page value) and pagination. The one remaining hole is the mismatch between the referenced issue_code/limit arguments and an input schema that declares no parameters, which leaves the calling convention underspecified.

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 description introduces two parameter concepts, issue_code (required, tied to the parent issue) and limit (max 200), which is real semantic value. However, the supplied input schema declares a bare object with no properties at all, creating ambiguity about how issue_code and limit are actually supplied — a reader cannot tell whether they are path, query, or body arguments.

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 ("The exact URLs affected by one issue") and clarifies the relationship to the sibling issue list by framing the output as "each offending url with the per-page value." An agent can distinguish this from list_site_audit_issues without opening either schema.

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 entry condition ("pass its issue_code") that implies this is a drill-down after listing issues, and the closing sentence frames the use case as building a fix list. It stops short of naming an explicit alternative or stating when not to use it, but the usage context is unambiguous.

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