Skip to main content
Glama

Read a saved crawl's data

writ_saved_crawl_data
Read-onlyIdempotent

Reads the data a saved crawl collected on its last completed run, without 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_saved_crawl_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
crawlYes
limitNo
outputNo
preview_charsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / output
      Added value: +{
      +  "type": "object"
      +}
    • addedInput schema / properties / preview_chars
      Added value: +{
      +  "type": "integer"
      +}
  2. Changed4 schema fields changed
    • removedInput schema / properties / crawl / description
      Removed value: -"Saved crawl slug, name, or id."
    • removedInput schema / properties / limit / description
      Removed value: -"Rows to return (default 25)."
    • 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 string cells (page markdown) to this many characters (default 2000; 0 = full cells). Full single pages: writ_workflow_data(refs=...) per the response hint.",
      -  "type": "integer"
      -}
  3. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real value beyond that by disclosing that only the last completed run's data is returned and that no crawling is triggered, which tells the agent this is a cheap cache read. It stops short of saying what happens when no run has completed or how results are paged.

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?

A single front-loaded sentence with no filler; the scope qualifier ('last completed run') and the cost signal ('without crawling') both land immediately. Nothing 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 no output schema, 0% schema description coverage, and a nested object parameter, the description leaves major gaps: return shape, pagination behavior, defaults for limit/preview_chars, and behavior when no completed run exists. For a four-parameter tool with a nested object, this is under-specified.

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 description coverage is 0% across four parameters, including a nested 'output' object and ambiguous 'limit' and 'preview_chars' fields. The description provides no meaning for any of them, so an agent has no way to know what limit applies to, what the output object configures, or what preview_chars truncates.

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: reads the data a saved crawl collected, explicitly scoped to its last completed run. The phrase 'without crawling' implicitly separates it from writ_run_saved_crawl, though it never names that sibling outright.

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?

'Without crawling' hints at the use case (retrieve existing results rather than re-run), but there is no explicit when-to-use or when-not guidance, and no alternative tool is named. The agent must infer that writ_run_saved_crawl is the contrasting choice.

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.