Skip to main content
Glama
Sign In
PageSift

PageSift

by YOLOW92
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Poll a job

pagesift_poll_job
Read-onlyIdempotent

Poll a crawl or batch-scrape job to get its status, progress, and pages collected so far; poll again while scraping and stop when status is final.

Instructions

Get the status, progress and pages collected so far for a pagesift_crawl or pagesift_batch_scrape job. status is scraping, completed, cancelled or failed; completed, cancelled and failed are final. While scraping, poll again after a few seconds; stop when the status is final. Pages collected so far are in data and remain available for 24 hours. Use pagesift_cancel_job to stop a running job.

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

Input Schema

NameRequiredDescriptionDefault
idYesJob id returned by pagesift_crawl or pagesift_batch_scrape.

Output Schema

NameRequiredDescriptionDefault
dataYesPages collected so far.
totalYesPages known so far; grows during a crawl.
errorsNoNumber of page-level errors recorded so far.
statusYesJob state. completed, cancelled and failed are final.
completedYesPages completed so far, including failed pages.
expiresAtYesWhen the job and its pages are removed (24 hours after creation).
robotsBlockedNoURLs skipped because robots.txt disallows them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.2

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description correctly focuses on behavior the annotations cannot express: the status vocabulary, which states are terminal, the polling cadence, and the 24-hour retention window for collected pages. It stops short of describing response shape, but an output schema exists to carry that.

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 compact sentences, front-loaded with what is returned and immediately followed by lifecycle rules. Every sentence carries a distinct actionable fact — statuses, terminality, poll cadence, retention, and the cancel alternative — with no restatement of 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?

For a single-parameter polling tool with full schema coverage, an output schema, and complete annotations, the description supplies exactly the missing operational context: terminal states, retry cadence, and how long results persist. Nothing an agent needs to call or re-call this correctly is absent.

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

Parameters4/5

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

Schema coverage is 100% and the single parameter is documented in the schema as a job id. The description reinforces provenance by tying the id to the producing tools (pagesift_crawl / pagesift_batch_scrape), which is slightly more than the schema states, so it edges above the baseline without adding format or validation details.

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 and resource: 'Get the status, progress and pages collected so far' for a named job type. It scopes the tool to jobs produced by pagesift_crawl or pagesift_batch_scrape, which cleanly separates it from the sibling tools that create those jobs.

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 gives an explicit operating loop ('poll again after a few seconds; stop when the status is final') and names a concrete alternative with its condition: 'Use pagesift_cancel_job to stop a running job.' An agent knows both when to call this repeatedly and when to switch tools.

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