Skip to main content
Glama

Run a saved crawl

writ_run_saved_crawl

Runs a saved crawl; max_age returns its recent data at no cost instead of re-crawling.

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": "<crawl>"
    },
    "name": "writ_run_saved_crawl"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNoHold until done.
crawlYes
limitNo
outputNo
max_ageNoReuse a run younger than this (seconds).
preview_charsNo
timeout_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
      +  "type": "integer"
      +}
    • 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. Changed7 schema fields changed
    • removedInput schema / properties / crawl / description
      Removed value: -"Saved crawl slug, name, or id (from writ_saved_crawls)."
    • removedInput schema / properties / limit
      Removed value: -{
      -  "description": "Rows of collected data to include (default 50).",
      -  "type": "integer"
      -}
    • changedInput schema / properties / max_age / description
      Previous value: -"Reuse the last completed crawl if it finished within this many seconds. 0 (default) always re-crawls."New value: +"Reuse a run younger than this (seconds)."
    • 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 each inline page's text cells to this many characters (default 12000; 0 = full). Full page: writ_workflow_data(workflow_id=<data_workflow_id>, refs=[...]).",
      -  "type": "integer"
      -}
    • removedInput schema / properties / timeout_seconds
      Removed value: -{
      -  "description": "Max seconds to wait when wait=true.",
      -  "type": "integer"
      -}
    • changedInput schema / properties / wait / description
      Previous value: -"Hold until the crawl converges (default false: a crawl is slow)."New value: +"Hold until done."
  3. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is largely covered. The description adds genuinely new behavior in the cost model (reusing recent data is free), but says nothing about async execution, polling via writ_crawl_status, what wait does, or timeout behavior.

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 front-loaded sentence with no filler; the cost caveat is attached efficiently to the parameter it modifies. It is arguably too sparse rather than padded, but nothing present is wasted.

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 seven parameters, a nested object, no output schema and low schema description coverage, the definition is far too thin. An agent cannot tell what limit, output, preview_chars or wait control, nor what the call returns or how to poll for completion.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 29%, so the description carries a heavy burden, yet it explains only max_age — which the schema already documents. The other six parameters (wait, limit, output, preview_chars, timeout_seconds) get no explanation, including the nested output object, so the coverage gap is not compensated.

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 ("Runs a saved crawl"), which is clearly distinct from data-retrieval or management siblings such as writ_saved_crawl_data and writ_update_saved_crawl. It stops short of distinguishing itself from writ_run_workflow or writ_crawl_site, but the core action is unambiguous.

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 max_age clause implies a when-to-use choice between forcing a fresh crawl and reusing recent data, which is useful implied guidance. However, there is no explicit statement of when to run this tool versus writ_crawl_site, writ_run_workflow, or writ_saved_crawl_data, and no prerequisites or exclusions are given.

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.