Skip to main content
Glama

Check a crawl

writ_crawl_status
Read-onlyIdempotent

Status of a crawl by crawl_id; wait=true holds up to 75 s and returns the collected rows when it converges.

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": {
      "crawl_id": "<crawl_id>"
    },
    "name": "writ_crawl_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNoHold until done and inline the rows.
limitNo
outputNo
crawl_idYes
preview_charsNo
timeout_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / output
      Added value: +{
      +  "type": "object"
      +}
    • addedInput schema / properties / preview_chars
      Added value: +{
      +  "type": "integer"
      +}
    • addedInput schema / properties / timeout_seconds
      Added value: +{
      +  "type": "integer"
      +}
  2. Changed6 schema fields changed
    • removedInput schema / properties / crawl_id / description
      Removed value: -"Crawl id from writ_crawl_site."
    • removedInput schema / properties / limit / description
      Removed value: -"Rows to inline when it converged (default 50)."
    • removedInput schema / properties / output
      Removed value: -{
      -  "description": "Response shape, for an answer a program or an API consumes rather than a reader. {shape: 'envelope' (default: Writ's full answer, projected) | 'table' ({columns, rows, total}) | 'records' (bare list of records) | 'record' (the newest record alone: one entity, a usage meter, a dashboard), fields: ['used', 'percent_used as pct', 'items.0.price as first_price'] (ordered pick, renames, dotted paths; a missing path is null, so keys are stable), exclude: ['depth'], include_meta: false (page metadata content_kind/depth/thumbnails is stripped unless true), key: 'usage' (wrap)}. On writ_crawl_site with save_as it is saved as the API's default shape.",
      -  "properties": {
      -    "exclude": {
      -      "items": {
      -        "type": "string"
      -      },
      -      "type": "array"
      -    },
      -    "fields": {
      -      "items": {
      -        "type": "string"
      -      },
      -      "type": "array"
      -    },
      -    "include_meta": {
      -      "type": "boolean"
      -    },
      -    "key": {
      -      "type": "string"
      -    },
      -    "shape": {
      -      "enum": [
      -        "envelope",
      -        "table",
      -        "records",
      -        "record"
      -      ],
      -      "type": "string"
      -    }
      -  },
      -  "type": "object"
      -}
    • removedInput schema / properties / preview_chars
      Removed value: -{
      -  "description": "Cut inline text cells to this many chars (default 12000; 0 = full).",
      -  "type": "integer"
      -}
    • removedInput schema / properties / timeout_seconds
      Removed value: -{
      -  "description": "Ceiling for wait=true (≤75).",
      -  "type": "integer"
      -}
    • changedInput schema / properties / wait / description
      Previous value: -"Hold until the crawl is terminal and inline its rows (default false)."New value: +"Hold until done and inline the rows."
  3. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already cover the read-only, idempotent, non-destructive safety profile, so the description's contribution is the real value: a 75-second block cap and the fact that rows are inlined on convergence. It still does not say what is returned before convergence, or whether repeated calls advance the crawl.

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?

A single semicolon-joined sentence with the resource and the blocking behavior front-loaded and no filler. It is efficient, though the compression contributes to the parameter gaps noted elsewhere.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With six parameters, a nested output object, no output schema, and no description of the non-blocking return shape, the definition is thin for the tool's complexity. An agent cannot tell from this text what a converged versus unconverged response looks like, or how the timeouts interact.

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 coverage is only 17%, so the description has to carry weight, and it does cover crawl_id and the wait semantics including a 75-second bound. However, limit, output, preview_chars, and timeout_seconds go undocumented, and the relationship between timeout_seconds and the stated 75-second wait cap is left ambiguous.

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?

The description names a specific verb-and-resource pair: it returns crawl status keyed by crawl_id. It is clear enough to separate from siblings like writ_crawl_files or writ_crawl_site, but it never explicitly says which sibling to use for file output or for starting a crawl, leaving that distinction implicit.

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 clause about wait=true implies usage for the blocking case, but there is no explicit guidance on when to poll versus block, nor any stated alternative or exclusion. An agent must infer the polling pattern on its own.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.