Skip to main content
Glama

scrapewise_get_matcher_history

Read-onlyIdempotent
        Lists the group's matching runs and stored drafts, newest first: one row per run that finished,
        failed or was stopped (kept even after a later save replaced it), plus the live job while it is a
        draft or still running. Each row carries the full setup that run used, so an earlier setup can be
        read here and saved again with scrapewise_update_matcher_job. Read-only; costs nothing.

        Args:
          - id (string, path, required): the group's id.
          - withDeleted (boolean, query, optional): true also lists runs hidden by "delete all matching
            data". Default false.
          - customerRef (string, query, optional): only for a Scrapewise admin key while the admin works in
            another customer's account (Take Over): the customerUniqueRef of that customer. Required then
            (409 TAKE_OVER_ACTIVE without it); leave it out otherwise.

        Returns:
          A list of MatcherJobDTO: id, status, masterData, scope, scopeScraperIdByJobId, created,
          expectedRowCount (matched rows of a finished run), failureReason, configId, and on a finished
          run of the newer engine setupSnapshot (setupSource db / file / default, activeVersion, setupHash:
          two runs with the same setupHash ran the same setup). When run choices are on: runChoices {auto,
          manual, requestedAt, startId, scheduled}, keptCount, keptDropped, verdictApply {applied, unapplied,
          late}, ledgerStatus, and on a run that started fresh freshCutoffAt, freshCurrent (undo allowed),
          freshUndone. Absent = not recorded.

        Examples:
          - Use when: "what did the last three matching runs of group {id} use?".
          - Use when: restoring an earlier setup (read the row, swap in the newest run ids, save).
          - Don't use when: you only need the current setup -> scrapewise_get_matcher_job.

        Error Handling:
          - 400 (CustomerError): no group with this id for this customer.
          - 409 TAKE_OVER_ACTIVE: this key's admin works in another customer's account — end Take Over or
            send customerRef=<that customer's ref>.
          - 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": {
      "id": "<id>"
    },
    "name": "scrapewise_get_matcher_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe group's id.
customerRefNoAdmin keys in Take Over only: the customerUniqueRef of the customer the admin works for. Required then; leave it out otherwise.
withDeletedNotrue also lists runs hidden by "delete all matching data". Default false.

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 / withDeleted / description
      Added value: +"true also lists runs hidden by \"delete all matching data\". Default false."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive, but the description adds real behavior: rows are kept even after being replaced by a later save, the call "costs nothing", and errors are enumerated with the 409 TAKE_OVER_ACTIVE condition tied to customerRef. The only gap is that it doesn't reconcile the enumerated return fields with the runtime hint that the response shape is dynamic.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well front-loaded with purpose first, then args, returns, examples, and errors. However, the Args section duplicates a fully-described schema, and the Returns enumeration of many DTO fields is long and sits awkwardly against the runtime hint that the agent should not rely on any specific field.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden of explaining returns and does so thoroughly, and it documents all required/optional params and the main failure modes. The remaining weakness is the mismatch between the fixed field list and the stated dynamic response shape.

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 coverage is 100%, so the Args block largely restates the schema descriptions. It does add the concrete error consequence (409 TAKE_OVER_ACTIVE if customerRef is omitted during Take Over) and ties withDeleted to the "delete all matching data" action, but that is incremental rather than compensating value.

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 ("Lists the group's matching runs and stored drafts") plus ordering ("newest first") and the exact row scope (finished, failed, stopped, plus live draft/running job). It is immediately distinguishable from the sibling that returns only the current setup.

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 explicit "Use when" scenarios (last three runs, restoring an earlier setup) and an explicit "Don't use when" that names the alternative tool, scrapewise_get_matcher_job. The agent is routed without inference, and the save-again path via scrapewise_update_matcher_job is spelled out.

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.