fairquery-web

Official

by fairquery

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

XML sitemap discovery and URL listing (free, paged)

web_sitemap_info

Read-onlyIdempotent

Discover a site's XML sitemap and inspect its URLs with lastmod dates. List indexed pages, filter by substring, sort by recency, and page through results without crawling.

Instructions

Find a site's XML sitemap (robots.txt Sitemap: lines, then /sitemap.xml, /sitemap_index.xml, or an explicit sitemapUrl), report whether it is a sitemap index, list child sitemaps, and page through the contained URLs with lastmod. For an index, the first maxChildSitemaps children are expanded. WHEN TO USE: count/inspect indexed pages, find recently modified URLs (filter with contains / sort), feed URLs into web_seo_audit. Not a crawler: only what the sitemap lists. Fetching: read-only GETs from this server with User-Agent "FairqueryBot ... Fairquery-MCP", 15 s timeout per request, body capped (1.5 MB HTML), max 5 redirects; URLs resolving to private/loopback/link-local addresses are refused (SSRF guard). Free, no token, no JavaScript rendering. Sitemap files are capped at 10 MB each (meta.truncated=true when cut). RETURNS: {count, total, offset, hasMore, nextOffset, meta{origin, sitemap_url, declared_in_robots, is_index, child_sitemap_count, child_sitemaps[], expanded_child_sitemaps[], truncated}, items[{type:"url", loc, lastmod, sitemap}]}. Errors: SITEMAP_NOT_FOUND plus INVALID_URL, BLOCKED_PRIVATE_ADDRESS, DNS_FAILED, FETCH_FAILED, TIMEOUT, TOO_MANY_REDIRECTS. WHEN NOT TO USE: not a crawler and does not audit pages - pass selected URLs to web_seo_audit; for AI-bot robots.txt rules use web_ai_crawler_access. COST: free - runs locally in this MCP server (direct HTTP GETs), no APIFY_TOKEN, no Apify billing. EXAMPLE: {"url":"python.org","contains":"/blog/","sort":"lastmod_desc","limit":10} -> paged url rows with loc and lastmod.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	Required. One public domain or http(s) URL, e.g. "vercel.com" or "https://www.python.org/about/". Bare domains are fetched over https; private/loopback hosts are refused.
`sort`	No	"sitemap" = file order (default); "lastmod_desc" = most recently modified first
`limit`	No	Optional page size: number of items to return, integer 1-1000 (default 100)
`offset`	No	Zero-based offset into the full result list (default 0); use nextOffset from the previous page
`contains`	No	Only URLs containing this substring, e.g. "/blog/"
`sitemapUrl`	No	Explicit sitemap URL to use instead of auto-discovery
`maxChildSitemaps`	No	For sitemap indexes: how many child sitemaps to fetch and list URLs from (default 3, max 20; 0 = list children only)

Output Schema

TableJSON Schema

Name	Required	Description
`meta`	No	Tool-specific context (company, source_url, ...)
`count`	Yes	Number of items in this page
`items`	Yes	Result rows for this page
`total`	Yes	Total items matching the filters (before paging)
`offset`	Yes	Offset of the first item in this page
`hasMore`	Yes	True if more items exist after this page
`nextOffset`	Yes	Offset to pass for the next page, or null

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.2.1Oct 17, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description exceeds them with concrete operational detail: User-Agent string, 15s timeout, 1.5MB body cap, max 5 redirects, SSRF guard refusing private/loopback addresses, 10MB per-sitemap cap with meta.truncated flag, and a full error-code list.

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?

Front-loads purpose then groups content under WHEN TO USE / RETURNS / WHEN NOT TO USE / COST / EXAMPLE, so navigation is easy. It is somewhat long, and the RETURNS block partially duplicates the existing output schema, but nearly every sentence carries actionable information.

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?

Covers discovery order, index handling, paging semantics, limits, SSRF/timeout behavior, error conditions, cost/auth, and a concrete example. With an output schema present it did not need to restate return shape, yet nothing an agent needs to invoke it correctly is missing.

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?

Schema description coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: explains that for an index only the first maxChildSitemaps children are expanded, that contains/sort drive filtering, and shows a worked example combining url, contains, sort, and limit.

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 specific verbs and resource: find a site's XML sitemap, report whether it is an index, list child sitemaps, page through URLs with lastmod. It explicitly differentiates from siblings by declaring 'Not a crawler' and routing to web_seo_audit and web_ai_crawler_access.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Has explicit WHEN TO USE (count/inspect indexed pages, find recently modified URLs, feed into web_seo_audit) and WHEN NOT TO USE (not a crawler, not an auditor; use web_seo_audit for pages, web_ai_crawler_access for robots.txt AI rules). Alternatives and conditions are named outright.

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

Deploy Server