Skip to main content
Glama
Sign In

ReadFetch

by com.readfetch
OverviewDiscussionsAdmin

readfetch_crawl_status

Read-only

FREE — no payment or wallet: Poll a crawl job started with readfetch_crawl. FREE — no payment or wallet; unauthenticated. Pass id from the crawl response. Returns job_id, status (queued, running, completed, or failed), completed/total counts, and a growing pages list (url plus Markdown) as results land. Stop polling when status is completed or failed. Results are kept for one hour after the job finishes.

Input Schema

NameRequiredDescriptionDefault
idYesJob id from readfetch_crawl (`job_id` in the start response). Required for MCP tools/call; poll until status is completed or failed (results kept ~1 hour).

Output Schema

NameRequiredDescriptionDefault
pagesNo
totalNo
job_idNo
statusNo
completedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"Job id returned by POST /v1/crawl."New value: +"Job id from readfetch_crawl (`job_id` in the start response). Required for MCP tools/call; poll until status is completed or failed (results kept ~1 hour)."
    • changedInput schema / required
      Previous value: -[]New value: +[
+  "id"
+]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "completed": {
+      "type": "integer"
+    },
+    "job_id": {
+      "type": "string"
+    },
+    "pages": {
+      "items": {},
+      "type": "array"
+    },
+    "status": {
+      "type": "string"
+    },
+    "total": {
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Adds substantive context beyond the readOnlyHint/openWorldHint annotations: no auth or payment required, the per-result retention window (one hour after finish), and that the pages list grows incrementally while running. That incremental-growth behavior is genuinely useful and is not derivable from annotations. Describing the return fields is partly redundant given the output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Polling purpose and stop condition are front-loaded, but "FREE — no payment or wallet" and the unauthenticated claim are duplicated verbatim in the same paragraph, and the field enumeration partly duplicates the output schema. Tightening to one sentence of cost/auth plus polling rules would lose nothing.

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 single-parameter polling tool with full schema coverage and an output schema, the description covers the prerequisite, the stopping rule, and result lifetime. A note on recommended polling cadence is the only meaningful 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% and the parameter doc already states the id comes from readfetch_crawl's job_id and the ~1 hour retention. The description repeats the same provenance ("Pass `id` from the crawl response") without adding format or extraction details, so 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?

States a specific verb and resource ("Poll a crawl job started with readfetch_crawl") and explicitly ties itself to the sibling that creates the job, so an agent can separate status polling from job creation without opening either schema.

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

Usage Guidelines4/5

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

Gives clear routing (use readfetch_crawl to start, this to poll) and an explicit stop condition ("Stop polling when status is completed or failed"). It does not spell out a polling interval or what to do on transient failures, so guidance is strong but not exhaustive.

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

All ReadFetch toolsInspect
Try in Browser
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources