Skip to main content
Glama
Sign In

Crawlwise

by site.crawlwise
OverviewDiscussionsAdmin

Crawl a site

crawl_site

Start a multi-page crawl of a site you own. Spends credits per page fetched (call estimate_cost with operation crawl and units = pages first). Returns a crawl id immediately. Does NOT run keyword or rank checks. Does NOT crawl the whole internet; it stops at the plan page cap. Orphans are not_measured when the crawl was capped.

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": {
      "site_id": "<site_id>"
    },
    "name": "crawl_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
pagesNoMost pages to fetch. Capped by the plan.
site_idYesA site id from list_sites.
allow_subdomainsNoAlso follow links to subdomains of the site.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / allow_subdomains / description
      Added value: +"Also follow links to subdomains of the site."
    • addedInput schema / properties / pages / description
      Added value: +"Most pages to fetch. Capped by the plan."
    • addedInput schema / properties / site_id / description
      Added value: +"A site id from list_sites."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, the description discloses credit consumption per page fetched, that the call returns a crawl id immediately, that it stops at the plan page cap, and that orphans are not_measured when capped. This tells the agent the tool's cost profile, async return behavior, and a key limitation.

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?

The description is front-loaded with the core action and prerequisite, and each subsequent sentence adds a distinct operational constraint. There is no filler.

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 non-destructive but credit-spending async crawl with no output schema, the description covers cost, immediate return value, plan cap, and orphan handling. It does not explicitly say how to retrieve results afterward, which would make it fully complete.

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 site_id, pages, and allow_subdomains. The description reinforces that pages are capped by the plan and maps pages to estimate_cost units, but it does not add meaning for site_id or allow_subdomains beyond the schema.

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?

The description gives a specific verb and resource: 'Start a multi-page crawl of a site you own.' It also distinguishes scope from adjacent capabilities by stating it does NOT run keyword or rank checks and does NOT crawl the whole internet.

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?

It states a clear prerequisite: call estimate_cost with operation crawl and units = pages first. It also defines when-not boundaries: not keyword/rank checks, not whole-internet crawling, and it stops at the plan page cap.

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

All Crawlwise toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources