XeoRank

get_crawl_results

Read-only

Get the pages and issues of a completed crawl, paged. Each list carries total/limit/offset; raise offset to read the rest, or filter issues by severity, category, rule_id or query to get every affected URL for one finding.

Input Schema

Name	Required	Description
`limit`	No	Rows per list (default 25 pages / 50 issues; max 500 pages / 1000 issues)
`query`	No	Issues only: substring match on the page URL or message
`detail`	No	Output verbosity: "concise" (default) trims long lists to top-25 and caps size; "detailed" returns the full result.
`job_id`	Yes	The crawl job ID
`offset`	No	Rows to skip in each list (default 0). Use with limit to page
`include`	No	Which lists to return: "both" (default), "pages" or "issues"
`rule_id`	No	Issues only: one rule id (e.g. OP-H-003) — returns every affected URL for that finding
`category`	No	Issues only: filter by category (e.g. on_page, technical, schema)
`severity`	No	Issues only: critical \| high \| medium \| low \| info
`page_filter`	No	Pages only: broken \| redirect \| thin

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 9, 2026

addedInput schema / properties / category

Added value: +{
+  "description": "Issues only: filter by category (e.g. on_page, technical, schema)",
+  "type": "string"
+}

addedInput schema / properties / include

Added value: +{
+  "description": "Which lists to return: \"both\" (default), \"pages\" or \"issues\"",
+  "type": "string"
+}

addedInput schema / properties / limit

Added value: +{
+  "description": "Rows per list (default 25 pages / 50 issues; max 500 pages / 1000 issues)",
+  "type": "number"
+}

addedInput schema / properties / offset

Added value: +{
+  "description": "Rows to skip in each list (default 0). Use with limit to page",
+  "type": "number"
+}

addedInput schema / properties / page_filter

Added value: +{
+  "description": "Pages only: broken | redirect | thin",
+  "type": "string"
+}

addedInput schema / properties / query

Added value: +{
+  "description": "Issues only: substring match on the page URL or message",
+  "type": "string"
+}

addedInput schema / properties / rule_id

Added value: +{
+  "description": "Issues only: one rule id (e.g. OP-H-003) — returns every affected URL for that finding",
+  "type": "string"
+}

addedInput schema / properties / severity

Added value: +{
+  "description": "Issues only: critical | high | medium | low | info",
+  "type": "string"
+}

First observedOct 7, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly=true, destructive=false, openWorld=true), so the bar is lower. The description adds genuine behavioral context the annotations lack: the paging model (each list carries total/limit/offset) and the fact that filtering by rule_id returns every affected URL rather than a paged slice.

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?

Two dense sentences, no filler, front-loaded with what is returned before the paging and filtering instructions. Slightly packed, but every clause carries operational information.

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?

For a 10-parameter, no-output-schema read tool, the description covers pagination, list selection, and filter behavior adequately. It stops short of characterizing what a 'page' or 'issue' record contains, which with no output schema would be the remaining useful addition.

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?

Schema description coverage is 100%, so the schema already documents all ten parameters including filtering semantics and defaults. The description's mention of severity/category/rule_id/query mostly restates the schema, adding only the 'every affected URL for one finding' framing. Baseline 3 applies.

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?

States a specific verb and resource — 'pages and issues of a completed crawl, paged' — which clearly distinguishes it from list_crawls (enumeration) and get_crawl_status (progress). It does not explicitly name those siblings, but the 'completed crawl' qualifier implies the boundary well enough for selection.

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?

Gives real usage guidance: use offset/limit to page, or filter issues by severity/category/rule_id/query to enumerate affected URLs for one finding. However, it never states when not to use this vs get_crawl_status, get_analysis, or list_crawls, nor that the crawl must already be complete before calling.

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

All XeoRank tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?