Skip to main content
Glama
Sign In
PageSift

PageSift

by YOLOW92
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Cancel a job

pagesift_cancel_job
Idempotent

Cancel a running crawl or batch scrape job to stop scheduling new pages while keeping already collected pages available for polling.

Instructions

Cancel a running pagesift_crawl or pagesift_batch_scrape job. Use pagesift_poll_job to read a job and pagesift_cancel_job to stop it. No new pages are scheduled; pages already collected stay available through pagesift_poll_job, and work that finishes after the cancel is discarded. A completed, failed or already cancelled job is left unchanged and its current status is returned, so repeated calls are safe. An unknown or expired id is an error.

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

Input Schema

NameRequiredDescriptionDefault
idYesJob id returned by pagesift_crawl or pagesift_batch_scrape.

Output Schema

NameRequiredDescriptionDefault
totalYesPages known when the request was handled.
statusYesState after the request; finished jobs keep their state.
successYesThe job exists and the cancel request was accepted.
completedYesPages completed when the request was handled.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.2

TDQS

A4.9/5.0
Behavior5/5

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

Annotations declare idempotentHint=true and destructiveHint=false; the description corroborates both rather than contradicting them, explaining that repeated calls are safe and terminal-state jobs are returned unchanged. It adds information annotations cannot carry: no new pages are scheduled, already-collected pages remain readable via pagesift_poll_job, and in-flight work finishing after cancel is discarded — the key side effect an agent must weigh before calling.

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 tight sentences, front-loaded with the action and scope, then sibling routing, then side effects, then edge cases. No filler and no repetition 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?

An output schema exists so return values need not be explained, yet the description still notes that current status is returned on a no-op cancel. Combined with the side-effect and error disclosure, nothing an agent needs to invoke this safely is missing.

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 id parameter is already documented, so the baseline is 3. The description goes slightly beyond by tying the accepted id space to the two producing tools and by specifying the failure mode for unknown or expired ids, which the schema does not state.

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 ("Cancel a running pagesift_crawl or pagesift_batch_scrape job") and explicitly limits scope to two job types, which cleanly separates it from the other crawl/scrape siblings. An agent can identify the operation without opening the 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?

Explicitly routes between siblings: "Use pagesift_poll_job to read a job and pagesift_cancel_job to stop it." It also states the no-op condition (already completed/failed/cancelled) and the error condition (unknown or expired id), giving concrete when-to-use and when-not-to-expect-effect guidance.

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