Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

web_crawl_results

Read committed crawl outcomes. Reads committed outcomes in stable publication order. While running, has_more=false only means the job is currently drained; poll again with next_cursor to observe later outcomes.

Instructions

Read committed crawl outcomes. Reads committed outcomes in stable publication order. While running, has_more=false only means the job is currently drained; poll again with next_cursor to observe later outcomes. Each response is bounded to 1 MiB.

Input Schema

NameRequiredDescriptionDefault
limitNoOutcomes per page
cursorNoOpaque owner-bound cursor
job_idYesOwned crawl job ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.12

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does so well: it discloses that only committed outcomes are returned, that order is stable publication order, that has_more=false during a run only means the job is currently drained, and that each response is capped at 1 MiB. These are exactly the non-obvious traits an agent needs; error/permission behavior is the only notable omission.

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?

Four short sentences, front-loaded with purpose then behavior. The first two sentences partially restate each other ('Read committed crawl outcomes' / 'Reads committed outcomes in stable publication order'), a small redundancy, but the remaining content is dense and earns its place.

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

Completeness4/5

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

There is no output schema, yet the description covers the key return semantics (stable order, has_more meaning while running, 1 MiB bound) and the pagination loop an agent must run. It omits any mention of authentication/ownership requirements or failure modes, which keeps it shy of a 5.

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%, so the schema already documents job_id, limit, and cursor, making 3 the baseline. The description adds context around cursor-based paging but no format or constraint detail beyond the schema, and it refers to `next_cursor` while the input param is named `cursor`, which is a minor terminology mismatch.

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 ('Read committed crawl outcomes'), which cleanly separates it from web_crawl (starts a job), web_crawl_status (reports status), and web_crawl_cancel (cancels). It leaves the sibling routing implicit rather than naming alternatives, so it earns a 4 rather than a 5.

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?

It implies the polling workflow ('poll again with `next_cursor`') and the running-job condition, which is useful usage context. However, it never explicitly says when to call this versus web_crawl_status, nor does it state the prerequisite that the job must be owned/completed, so guidance remains implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools