Skip to main content
Glama

Edit a saved crawl

writ_update_saved_crawl
DestructiveIdempotent

Inspects or changes a saved crawl's settings in place.

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_update_saved_crawl"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
crawlYes
settingsNoSparse settings patch.
descriptionNo
default_max_age_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / default_max_age_seconds
      Added value: +{
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / description
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / name
      Added value: +{
      +  "type": "string"
      +}
  2. Changed5 schema fields changed
    • removedInput schema / properties / crawl / description
      Removed value: -"Saved crawl slug, name, or id."
    • removedInput schema / properties / default_max_age_seconds
      Removed value: -{
      -  "minimum": 0,
      -  "type": "integer"
      -}
    • removedInput schema / properties / description
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / name
      Removed value: -{
      -  "type": "string"
      -}
    • changedInput schema / properties / settings / description
      Previous value: -"Sparse crawl config patch merged recursively into the complete saved settings."New value: +"Sparse settings patch."
  3. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description's only added behavioral signal is "in place," implying mutation without creating a new crawl. It does not disclose what a destructive edit can overwrite, whether omitted fields are preserved, or any permission requirements — significant gaps for a destructive write. The word "inspects" also implies read behavior that sits awkwardly against readOnlyHint=false.

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?

A single short sentence with no filler, which is structurally clean, but its brevity comes at the cost of under-specification rather than economy. The most important information (patch semantics, destructive scope) is absent rather than front-loaded.

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?

For a destructive, idempotent write tool with a nested object parameter, 20% schema coverage, and no output schema, the description is far too thin. An agent cannot tell what a call will change, what is preserved, or what it returns.

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 only 20% across 5 parameters, including a nested settings object documented only as "Sparse settings patch." The description does not explain the sparse-patch merge semantics, what the required crawl identifier accepts, or what name/description/default_max_age_seconds do, so it fails to compensate for the coverage gap.

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?

States a verb and resource ("changes a saved crawl's settings in place"), which is more specific than the title alone, but "inspects or changes" muddies whether this is a read or a write and never says which settings are editable. It also does not distinguish itself from siblings such as writ_update_workflow or writ_run_saved_crawl.

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 guidance, no mention of prerequisites (e.g., the crawl must already exist), and no routing to alternatives like writ_run_saved_crawl or writ_saved_crawls. The agent must infer the tool's role from the name alone.

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.