Skip to main content
Glama
Sign In
spidra-io

spidra-mcp-server

Official
by spidra-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

spidra_map

Read-only

Lists a website's page URLs from its sitemaps and page links without scraping, so you can search, filter, and choose which pages to read instead of crawling the site.

Instructions

List a website's page URLs without scraping them, from its sitemaps and the links on its pages. Waits and returns the URLs, usually in a few seconds.

Use it when you need the right pages on a site before reading them ("which page on stripe.com covers refunds?"), or a full list of a site's URLs. Then: pick the URLs you need and read exactly those with spidra_scrape or spidra_batch_scrape. That's usually cheaper than spidra_crawl when you only need a few pages.

  • "search" keeps only matching URLs, best matches first. Keep "limit" small when you only need a few.

  • "total" is how many URLs matched; "scanned" is how many were found in all.

Cost: 1 credit per call. Free when no URLs are found.

Example: {"url": "https://docs.python.org/3/", "search": "asyncio", "limit": 20}

Input Schema

NameRequiredDescriptionDefault
urlYesThe website to map
limitNoMost URLs returned (default 500)
searchNoOnly URLs related to these words, best matches first
cookiesNoCookies from the user's own signed-in browser session, for pages behind a login, e.g. "session=abc; token=xyz". Never stored.
sitemapNo"include" (default) uses the sitemap and page links, "only" the sitemap (fastest), "skip" only the links
respectRobotsNoLeave out URLs the site's robots.txt disallows
ignoreQueryParamsNoTreat URLs that differ only by query string as one (default true)
includeSubdomainsNoAlso list URLs on subdomains

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only cover readOnlyHint and openWorldHint, but the description adds latency expectations ('usually in a few seconds'), a precise billing model ('1 credit per call, free when no URLs are found'), result ordering, and the meaning of 'total' vs 'scanned'. These are exactly the traits annotations cannot express.

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?

Front-loaded with the one-sentence purpose, then bolded 'Use it when' / 'Then' routing, then bullets, then cost and example. Every line carries decision-relevant information for an 8-parameter tool with sibling competition.

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?

No output schema exists, and the description compensates by defining 'total' and 'scanned' and the shape of results conceptually. Combined with full schema coverage and the safety annotations, an agent has everything needed to call this correctly.

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 coverage is 100%, so the baseline is 3. The description still adds value beyond the schema by explaining that 'search' orders best matches first and that 'limit' should be kept small when only a few are needed, plus a worked example showing the three most important params together.

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 ('List a website's page URLs') plus the mechanism ('from its sitemaps and the links on its pages') and explicitly says it does NOT scrape. This distinguishes it immediately from spidra_scrape, spidra_crawl, and spidra_batch_scrape.

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?

Gives a concrete when-to-use scenario ('which page on stripe.com covers refunds?'), a follow-up recipe (pick URLs, read with spidra_scrape or spidra_batch_scrape), and an explicit cost-based exclusion against spidra_crawl. Nothing is left to inference.

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