Skip to main content
Glama

List a crawl's captured files

writ_crawl_files
Read-onlyIdempotent

The original files (PDFs, office documents, images, CSVs) a crawl captured, with short-lived download URLs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "writ_crawl_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
runsNo
crawlNo
limitNo
crawl_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
      +  "type": "integer"
      +}
    • addedInput schema / properties / runs
      Added value: +{
      +  "type": "integer"
      +}
  2. Changed4 schema fields changed
    • removedInput schema / properties / crawl / description
      Removed value: -"Saved crawl slug, name, or id (alternative to crawl_id)."
    • removedInput schema / properties / crawl_id / description
      Removed value: -"Crawl id from writ_crawl_site."
    • removedInput schema / properties / limit
      Removed value: -{
      -  "description": "Max files to return (default 100, cap 200).",
      -  "type": "integer"
      -}
    • removedInput schema / properties / runs
      Removed value: -{
      -  "description": "With `crawl`: how many recent completed runs to aggregate (default 1 — the current version of every document).",
      -  "type": "integer"
      -}
  3. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered structurally. The description adds one genuinely useful behavioral fact beyond that — the download URLs are short-lived — but says nothing about pagination behavior (despite a limit parameter) or whether results depend on crawl completion.

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?

One compact sentence with zero filler, and the useful detail (short-lived URLs) is included. Being a verbless fragment weakens the front-loading slightly, but 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 four undocumented parameters, no output schema, and no notes on crawl lifecycle or pagination, the description leaves too much unresolved for a tool whose selection hinges on crawl/crawl_id/runs. It covers the return content but not how to call it correctly.

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, and the description does not explain any of them. It never clarifies what distinguishes 'crawl' from 'crawl_id', what 'runs' selects, or how 'limit' bounds the result set, so the agent gets no help resolving these opaque names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource — the original files (PDFs, office documents, images, CSVs) a crawl captured — which goes beyond the bare title by enumerating content types. However, it is a noun phrase with no verb (list/retrieve) and it never distinguishes this from siblings such as writ_saved_crawl_data or writ_export_data, so an agent must infer the operation.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no prerequisites (e.g. that a completed crawl is required), and no named alternative for retrieving crawl output. The only hint is the implied framing of 'files a crawl captured', which leaves the agent to guess between this and the saved-crawl/export siblings.

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.