Skip to main content
Glama

commoncrawl_urls

Retrieve archived URLs for a domain from the Common Crawl index to uncover forgotten endpoints, old JavaScript bundles, and parameters without an API key.

Instructions

Find archived URLs for a domain in the Common Crawl index (keyless).

Great for forgotten endpoints, old JS bundles and parameters. Uses the latest crawl index unless index is supplied (e.g. CC-MAIN-2026-43-index).

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": {
      "domain": "<domain>"
    },
    "name": "commoncrawl_urls"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexNo
limitNo
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does deliver two useful behavioral facts: the endpoint is keyless (no auth required) and it defaults to the latest crawl index unless overridden. It omits result volume, pagination, and whether the limit truncates silently before defaulting to 500 — meaningful gaps for a three-parameter tool with zero annotation coverage.

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?

Three short sentences, front-loaded with the core purpose, and the parenthetical '(keyless)' efficiently conveys an auth fact in two words. The mid-sentence line break is a cosmetic defect rather than a comprehension problem, and nothing is obviously redundant.

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 small lookup tool with no output schema and no annotations, the description covers source, authentication model, index defaulting, and intended use case — most of what an agent needs to invoke it. The remaining gaps (domain format, limit behavior, result shape) are real but secondary given the tool's simplicity.

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 0%, so the description must compensate and it only partly does: it explains `index` semantics (defaults to latest crawl) and even gives a format example, CC-MAIN-2026-43-index, which is genuinely beyond the schema. `limit` and `domain` get no treatment — notably whether `domain` should be a bare host or a full URL, which is exactly the ambiguity an agent would hit first.

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 — 'Find archived URLs for a domain in the Common Crawl index' — and identifies the data source, which lets an agent distinguish it from similarly shaped siblings like wayback_urls or sitemap_urls by source. It stops short of naming those alternatives explicitly, so it is clear but not fully disambiguated.

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?

The line 'Great for forgotten endpoints, old JS bundles and parameters' gives reconnaissance-oriented use-case context, which implies when to reach for it. However, there is no explicit when-not, no prerequisite statement, and no comparison to the Wayback or sitemap alternatives that an agent would need to choose correctly between near-identical tools.

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