Skip to main content
Glama

Get crawl errors

get_crawl_errors
Read-onlyIdempotent

Read a paginated list of crawl errors by task id.

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": {
      "id": "<id>"
    },
    "name": "get_crawl_errors"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
debugNoKeep each item's usage and trace. Default false.
limitNo
cursorNo
fieldsNo
attemptIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / fields
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / debug
      Added value: +{
      +  "description": "Keep each item's usage and trace. Default false.",
      +  "type": "boolean"
      +}
  3. Added

TDQS

C2.9/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 the safety profile is fully covered elsewhere. The description adds only that results are paginated, and says nothing about cursor semantics, ordering, or how errors relate to a crawl attempt (attemptId).

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, which is the right shape for a list tool. It is terse to the point of omitting useful routing and paging detail, but nothing written 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 six parameters, 17% schema coverage, and no output schema, the description is too thin: it does not explain pagination mechanics (cursor/limit interplay), what a 'crawl error' record contains, or how attemptId narrows results. For a read tool this is workable but clearly under-documented.

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 17% — only 'debug' is documented in the schema — and the description only clarifies that 'id' refers to a task id. That leaves limit, cursor, fields, and attemptId with no meaning anywhere, which is a substantial gap the description should have filled.

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 ('Read'), resource ('crawl errors'), and a scoping key ('by task id'), so an agent knows exactly what comes back. It does not explicitly contrast itself with the sibling 'get_batch_errors', which handles the analogous batch case, so sibling differentiation is only inferable from the tool name.

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 prerequisites, and no mention of alternatives such as get_batch_errors or get_crawl for retrieving crawl status. An agent must infer the routing decision from the tool 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.