Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

web_crawl_results

Read-only

Retrieve retained crawl results in stable cursor order. Pass the owned job ID and poll the returned cursor while a job is running.

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": "web_crawl_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoOutcomes per page, 1 to 100; default 50.
cursorNoOpaque owner-bound cursor returned by web_crawl_results.
job_idYesrequired,Owned crawl job ID returned by web_crawl_submit.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real context beyond them: results are 'retained', ordering is 'stable', the job ID must be 'owned', and the cursor is meant to be polled 'while a job is running'. These ownership and polling behaviors are not in the annotations.

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?

Two sentences with zero waste: the purpose and ordering are front-loaded, followed by the essential invocation instruction. Nothing is padded or redundant.

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?

With an output schema present, return values need no explanation, and annotations cover safety. The description supplies purpose, ownership, and cursor-polling behavior, which is nearly complete for a paginated crawl-results tool; it could say more about completion/end-of-results handling but is largely sufficient.

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 all three parameters (limit, cursor, job_id) are already documented in the schema. The description reinforces the cursor-polling usage and the 'owned' constraint on job_id, but adds little syntax or format detail beyond the schema baseline.

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 ('Retrieve retained crawl results') plus an ordering guarantee ('stable cursor order'), so the agent knows exactly what it gets. It does not name or contrast with the sibling web_crawl_status, leaving the boundary between 'results' and 'status' to inference.

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?

'Pass the owned job ID and poll the returned cursor while a job is running' gives implied usage context and the polling condition. However it never states when to prefer this over web_crawl_status or how the two relate, so the tool-selection guidance is only implied rather than explicit.

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

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources