Skip to main content
Glama

Black SEO Analyzer

crawl_status

Read-only

Report the progress of a crawl started by start_crawl: state ("queued", "running", "finished" or "failed"), the crawl session_id to read results from, the pages stored so far, and the error text if it failed. Poll every few seconds; a queued crawl starts as soon as the worker is free. Do not call issues_summary or query_issues for that crawl until state is "finished", or you will read a partial result.

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": {
      "job_id": "<job_id>"
    },
    "name": "crawl_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesThe job id returned by start_crawl.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds behavior they cannot express: the four possible states, that a queued crawl begins when a worker frees up, recommended polling cadence, and the partial-result hazard. That is substantive context beyond structured fields rather than a restatement of them.

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?

Front-loads the purpose, then the returned fields, then the polling rule, then the failure-mode warning — each sentence carries distinct information. The enumerated state values are compact and necessary given there is no output schema; nothing is padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description must define the return payload, and it does so field by field. Combined with the polling and gating guidance, an agent has everything needed to call this correctly and interpret the response for a one-parameter read tool.

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

Parameters3/5

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

Schema description coverage is 100% and the single job_id parameter is already documented in the schema as "The job id returned by start_crawl." The description reinforces that lineage ("a crawl started by start_crawl") but adds no format, sourcing, or validation detail beyond what the schema states, so the high-coverage baseline of 3 applies.

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

Purpose5/5

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

States a specific verb and resource ("Report the progress of a crawl") and anchors it to the originating tool ("started by start_crawl"). It then enumerates exactly what is reported: state, session_id, pages stored, error text — enough for an agent to distinguish it from list_crawls or issues_summary without opening any schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use guidance ("Poll every few seconds") plus a concrete exclusion naming two siblings: do not call issues_summary or query_issues until state is "finished". The consequence of ignoring the exclusion (partial results) is spelled out, so the routing decision is fully determined.

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.