Skip to main content
Glama

scrapewise_update_matcher_fresh_undo

Idempotent
        Undoes "start fresh" (manualMatches=FRESH) of a finished matching run of the group: the review decisions
        made before that run count again in the review list and in the next run. It does not start a run and
        does not change any match result now. Only the newest start fresh of the setup can be undone. Calling it
        again answers the same (nothing changes twice).

        Args:
          - id (string, path, required): the group's id.
          - runId (string, path, required): the run that started fresh (history row with freshCurrent=true).
          - idempotency_key (string, query): REQUIRED for AI-agent keys. A new value for each new undo; the same
            value only to retry it.
          - customerRef (string, query, optional): admin key in Take Over only: that customer's
            customerUniqueRef.

        Returns:
          {runId, configId, cutoffAt, undone: true, undoneAt}.

        Examples:
          - Use when: "bring back my review decisions in group {id}" after a run that started fresh.
          - Don't use when: you want to know which run started fresh -> scrapewise_get_matcher_history
            (freshCurrent, freshUndone).

        Error Handling:
          Nothing was changed in each.
          - 400 IDEMPOTENCY_KEY_REQUIRED: an AI-agent key sent no idempotency_key.
          - 404 NotFound: no such run in this group, or this run did not start fresh.
          - 409 FRESH_NOT_CURRENT: a newer start fresh is in place; only the newest can be undone.
          - 409 TAKE_OVER_ACTIVE: end Take Over or send customerRef.
          - 401 Unauthorized; 403 for a read-only key or a plan without matching.

[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": {
      "id": "<id>",
      "runId": "<runId>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "scrapewise_update_matcher_fresh_undo"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe group's id.
runIdYesthe run that started fresh (history row with freshCurrent=true).
customerRefNoAdmin keys in Take Over only: the customerUniqueRef of the customer the admin works for. Required then; leave it out otherwise.
idempotency_keyYesRequired for AI-agent keys: a new value per new undo, the same value only to retry it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / id / description
      Added value: +"the group's id."
    • addedInput schema / properties / runId / description
      Added value: +"the run that started fresh (history row with freshCurrent=true)."
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly=false, destructive=false, idempotent=true), and the description adds genuinely new behavior: what the undo does and does not affect (review decisions return, match results unchanged), that repeat calls are no-ops, the exact return shape, and enumerated error semantics including 409 FRESH_NOT_CURRENT, 409 TAKE_OVER_ACTIVE and 401/403 conditions.

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?

Well structured and front-loaded: the core constraint appears in the first sentence, followed by Args, Returns, Examples and Error Handling. Slightly padded by duplicating the Args block already fully documented in the schema, and the trailing runtime hint adds length, but no sentence misleads.

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 mutation tool with no output schema, the description supplies the return object shape, the idempotency contract, the newest-only limitation, and a full error catalog — everything an agent needs to call it correctly and interpret failures.

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%, so the baseline is 3, but the description adds meaning: runId must be a history row with freshCurrent=true, idempotency_key is mandatory specifically for AI-agent keys with a new-value-per-new-undo rule, and customerRef matters only in Take Over. This goes beyond the schema's own wording, though it largely restates the parameter list.

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 precise verb+resource: undoes a 'start fresh' (manualMatches=FRESH) on a finished matching run of a group, and immediately bounds the scope ('does not start a run and does not change any match result now'). An agent can distinguish it from the setup/history siblings without opening any 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' example and a 'Don't use when' routing rule pointing to scrapewise_get_matcher_history for discovering which run started fresh. It also states the hard precondition (only the newest start fresh is undoable) and the idempotency retry rule.

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.