Skip to main content
Glama

scrapewise_cancel_reapply_rules

DestructiveIdempotent
        Stops the run's active re-apply. A waiting job ends at once; a running one stops before its next batch
        of rows (within a few seconds). Rows already written keep their new values — nothing is rolled back
        and no column is removed. Calling it again, or on a run with no active re-apply, is harmless. Free
        (no credits). Start it again later with scrapewise_run_reapply_rules: it continues safely, rows that
        already have the new values are not written twice.

        Args:
          - jobId (string, path, required): the run's id (scraperJobStatusId).

        Returns:
          The latest job of the run with its state (CANCELLED once stopped, or still RUNNING for a moment
          until the current batch ends); 204 No Content when the run never had a re-apply.

        Examples:
          - Use when: "stop re-applying the rules to run {jobId}".
          - Don't use when: you want to stop a scrape → scrapewise_stop_scraper.

        Error Handling:
          - 400 (CustomerError) when the run does not exist for this customer.
          - 401 Unauthorized; 500 INTERNAL.

[runtime hint] This tool returns JSON-as-text — its response shape is dynamic (per-scraper itemsConfig, file binary, etc.) so the MCP outputSchema is omitted. Do not rely on the presence of any specific field in the response; treat the result as a string-or-object blob and parse defensively.

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": {
      "jobId": "<jobId>"
    },
    "name": "scrapewise_cancel_reapply_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYesthe run's id (scraperJobStatusId).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / jobId / description
      Added value: +"the run's id (scraperJobStatusId)."
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by describing exactly what happens to an in-flight job (a waiting job ends at once; a running one stops before its next batch, within seconds) and what is not undone (written rows keep new values, nothing rolled back, no column removed). It also discloses that repeat calls are harmless (reinforcing idempotentHint), that the call is free of credits, and enumerates error codes including 400 CustomerError.

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?

Front-loads the core effect and the rollback caveat in the first paragraph, then uses labeled sections (Args, Returns, Examples, Error Handling) that are easy to scan. It is on the long side for a single-parameter cancel tool, but nearly every sentence carries distinct information.

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?

Although no output schema exists, the description explains the return value (latest job with its state, CANCELLED or momentarily RUNNING, and 204 when there was never a re-apply). Combined with the success/idempotency semantics and the error table, an agent has everything needed to invoke and interpret the call.

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?

There is a single parameter at 100% schema description coverage, and the Args block restates exactly what the schema already says ("the run's id (scraperJobStatusId)") without adding format, sourcing, or lookup guidance. Baseline 3 is appropriate because the schema carries the parameter documentation.

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?

Opens with a precise verb+resource: "Stops the run's active re-apply," scoped to a re-apply operation on a specific run rather than the scraper itself. It explicitly names the sibling it is not (scrapewise_stop_scraper) so an agent can route correctly without opening either 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?

Provides an explicit "Use when" phrase and a "Don't use when: you want to stop a scrape → scrapewise_stop_scraper" exclusion naming the correct alternative. It also states the restart path (scrapewise_run_reapply_rules) and that re-invocation is harmless, so the agent knows both when and when not to call it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.