Skip to main content
Glama

scrapewise_update_matcher_history_settings

DestructiveIdempotent
        Sets runsKept: how many of the group's newest finished matching runs keep their list of matched and
        to-review pairs (the list scrapewise_get_matcher_run_pairs reads). Older runs stay in the history with
        their counts; only their pair list is removed. It does not start a run and does not change any match.

        Args:
          - id (string, path, required): the group's id.
          - idempotency_key (string, query): REQUIRED for AI-agent keys. A new value for each new change; the
            same value only to retry that same change.
          - body: {"runsKept": n}, n a whole number from 1 to 10. Without a change the group keeps 10.
          - customerRef (string, query, optional): admin key in Take Over only: that customer's
            customerUniqueRef.

        Returns:
          {runsKept}. scrapewise_get_matcher_config_status shows it as runsKept.

        Examples:
          - Use when: "keep only the last 3 runs of group {id}" -> {"runsKept": 3}.
          - Don't use when: you want to see a past run's pairs -> scrapewise_get_matcher_run_pairs.

        Error Handling:
          Nothing was changed in each.
          - 400 FIELD_INVALID (field runsKept): missing, or not from 1 to 10.
          - 400 IDEMPOTENCY_KEY_REQUIRED: an AI-agent key sent no idempotency_key.
          - 404 NotFound: an unknown group or another customer's group, or the setting is not offered yet.
          - 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>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "scrapewise_update_matcher_history_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe group's id.
bodyNo{"runsKept": n}, n a whole number from 1 to 10. Without a change the group keeps 10.
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 change, the same value only to retry it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / body / description
      Added value: +"{\"runsKept\": n}, n a whole number from 1 to 10. Without a change the group keeps 10."
    • addedInput schema / properties / id / description
      Added value: +"the group's id."
  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 supplied annotations (destructiveHint=true, idempotentHint=true) by saying exactly what is destroyed and what survives: only the pair list is removed while older runs keep their counts. It also documents idempotency-key retry semantics and enumerates error outcomes (FIELD_INVALID range, IDEMPOTENCY_KEY_REQUIRED, NotFound for unoffered settings, TAKE_OVER_ACTIVE, 401/403), which no annotation conveys.

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-loaded with the core behavior, then cleanly sectioned into Args, Returns, Examples, and Error Handling, with a runtime hint about the dynamic response. The 1-10 range and default-10 rule are restated in the Args block, the body block, and the error list, so some tightening is possible.

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?

Despite the absence of an output schema, the description documents the return value ({runsKept}) and where it surfaces (scrapewise_get_matcher_config_status), and the runtime hint warns that responses are dynamic JSON-as-text. For a destructive four-parameter mutation tool, all the operational context an agent needs is present.

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 text nearly mirrors the description (runsKept range 1-10 and default 10, customerRef Take Over semantics, idempotency_key retry rule). The description adds light emphasis ('REQUIRED for AI-agent keys') but little meaning the schema does not already carry, so baseline 3 applies.

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 ('Sets runsKept: how many of the group's newest finished matching runs keep their list of matched and to-review pairs') and immediately scopes it against siblings by naming the tool that reads those pairs. It also rules out confusable behaviors ('does not start a run and does not change any match').

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?

Includes an explicit 'Use when' example with a concrete input, and an explicit 'Don't use when' that routes to scrapewise_get_matcher_run_pairs for viewing a past run's pairs. The prerequisite cases (idempotency_key for AI-agent keys, customerRef during Take Over, read-only key rejection) are stated as conditions, not left to inference.

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.