Skip to main content
Glama
Sign In

Irmu

by com.irmu.app
OverviewDiscussionsAdmin

Collect a running crawl

crawl_poll
Read-onlyIdempotent

Collect a crawl that another tool answered with status "queued" or "running". Pass its job_id. Free. Returns the same status; when it is "done", the page is in content (as markdown with output) or the extracted result in data. Wait a few seconds between polls.

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

Input Schema

NameRequiredDescriptionDefault
job_idYesThe `job_id` a crawl, screenshot, google_ai_overview, booking, tripadvisor or airbnb tool answered with.
outputNoHow the page comes back in `content`: "html" verbatim, or "markdown" -- smaller and easier to read. Free either way.html
main_contentNoWith `output` "markdown" only: convert just the page's main block, without navigation, header, footer, sidebars or cookie banners. Falls back to the whole page when no main block with real text is found.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / job_id / description
      Previous value: -"The `job_id` a crawl, screenshot, google_ai_overview, booking or tripadvisor tool answered with."New value: +"The `job_id` a crawl, screenshot, google_ai_overview, booking, tripadvisor or airbnb tool answered with."
  2. Changed1 schema field changed
    • changedInput schema / properties / job_id / description
      Previous value: -"The `job_id` a crawl, screenshot, google_ai_overview or booking tool answered with."New value: +"The `job_id` a crawl, screenshot, google_ai_overview, booking or tripadvisor tool answered with."
  3. Changed2 schema fields changed
    • addedInput schema / properties / main_content
      Added value: +{
+  "default": false,
+  "description": "With `output` \"markdown\" only: convert just the page's main block, without navigation, header, footer, sidebars or cookie banners. Falls back to the whole page when no main block with real text is found.",
+  "type": "boolean"
+}
    • addedInput schema / properties / output
      Added value: +{
+  "default": "html",
+  "description": "How the page comes back in `content`: \"html\" verbatim, or \"markdown\" -- smaller and easier to read. Free either way.",
+  "enum": [
+    "html",
+    "markdown"
+  ],
+  "type": "string"
+}
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds genuinely new context beyond that: the call is free, it echoes back the same status rather than transitioning state, and the payload location differs by completion state (`content` vs `data`). It does not mention timeouts or how long a job may stay queued, which is the main remaining gap.

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?

Four short sentences, front-loaded with the identification condition, then input, cost, return shape, and polling cadence. Every sentence contributes a distinct fact and none restates the title.

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?

There is no output schema, so the description carries the return-value burden and does so: it names `status`, `content` (markdown or html), and `data`. Combined with the polling advice and the cross-tool `job_id` provenance, an agent has everything needed to call and interpret this 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 schema already explains `job_id`, the `output` enum, and `main_content` in detail, so the baseline is 3. The description only reinforces that you 'Pass its `job_id`' and lightly links `output` markdown to the returned `content`, adding little that the schema does not already carry.

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?

The description opens with a specific verb+resource ('Collect a crawl') and immediately scopes it to jobs that returned `status` "queued" or "running", which cleanly separates it from the sibling `crawl` that starts a job. The return contract ('Returns the same `status`; when it is "done", the page is in `content` ... or the extracted result in `data`') tells an agent exactly what it gets back.

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?

It states the precise precondition for use: another tool answered with `status` "queued" or "running", and you pass that `job_id`. It also gives operational guidance -- 'Wait a few seconds between polls' -- which is the one behavioral rule an agent needs to poll correctly.

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

All Irmu 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