Skip to main content
Glama
Sign In
contextfetch-mcp

contextfetch-mcp

by lachy3433
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ContextFetch site map

contextfetch_map
Read-only

List a website's URLs from sitemaps and start page links without fetching pages, to identify pages for extraction or crawling.

Instructions

List a website's URLs without fetching its pages: its sitemaps (from robots.txt, else /sitemap.xml) plus the start page's links, same site only, up to limit (<= 5,000). Use it to find the right pages before contextfetch_extract_url or contextfetch_crawl. Costs 1 credit.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "contextfetch_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL of the site (any page on it).
limitNoMaximum URLs (1-5,000, default 100).
exclude_pathsNoRegexes; never list URLs whose path matches one.
include_pathsNoRegexes; only list URLs whose path matches one, e.g. ["^/blog/"].

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only and open-world safety, and the description adds real context beyond them: a 1-credit cost, the source precedence (robots.txt before /sitemap.xml), and page-link fallback. It stops short of describing the response shape or what happens when no sitemap exists, so not a 5.

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?

Two dense sentences, zero filler: the mechanism and scope come first, the sibling routing second, the cost last. The 5,000 cap is the only mild restatement of schema.

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 4-param read-only tool with no output schema, the description covers sourcing, same-site restriction, limit, and billing — enough to call it correctly. It leaves the response format (bare URL list?) implicit, which is a minor but real gap.

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 url, limit, include_paths, and exclude_paths are already documented including ranges and regex semantics. The description only restates the limit cap and that url may be any page; it says nothing about the include/exclude filtering that the schema carries. Baseline 3 applies.

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?

Specific verb and resource: "List a website's URLs without fetching its pages," with the exact sources named (robots.txt sitemap, else /sitemap.xml, plus start-page links). The scope qualifier "same site only" and the limit cap make it unmistakable against page-returning siblings.

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?

Explicitly routes the agent: "Use it to find the right pages before contextfetch_extract_url or contextfetch_crawl," naming both the alternative tools and the sequencing condition. No inference required to pick this tool over its siblings.

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