Skip to main content
Glama

scrapewise_get_matcher_run_pairs

Read-onlyIdempotent
        Lists the product pairs that ONE finished matching run of the group found, as that run wrote them:
        its matches (kind=MATCH) or its to-review pairs (kind=REVIEW), in the run's own order, up to 500 per
        page. Use it to look at an older run from the history, also after a newer run replaced its matches.
        Read-only; costs nothing; a Read key may call it.

        Args:
          - id (string, path, required): the group's id.
          - runId (string, path, required): the run's id (runId from scrapewise_get_matcher_history).
          - kind (string, query, optional, default MATCH): MATCH | REVIEW.
          - page (integer, query, optional, default 0): the page, starting at 0.
          - size (integer, query, optional, default 100): pairs per page, 1 to 500.
          - 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:
          runId, kind, ledgerStatus, content, totalElements, page, size. ledgerStatus: COMPLETE (the whole
          list), TRUNCATED (the list hit its size limit; to-review pairs were cut first), PARTIAL (a part could
          not be stored) or NONE (this run keeps no pair list: an older run, or only the newest runs keep one) -
          then content is empty. Each pair: sourceScraperId, sourceIdentity (the shop row's ID value), masterRef
          (the main-list row), decision (MATCH / REVIEW), score (0-100 or null), matchOrigin (VERDICT = a person
          approved it, KEPT = kept from the run before, ENGINE), sourceTitle, masterTitle.

        Examples:
          - Use when: "which matches did last week's run have?", "show the pairs of run X".
          - Don't use when: you want the group's current matches -> scrapewise_get_match_evidence; the list of
            runs -> scrapewise_get_matcher_history.

        Error Handling:
          - 400 FIELD_INVALID: kind not MATCH / REVIEW, page below 0, or size not 1 to 500 (field names it).
          - 404 NotFound: no such run in this group for this customer (also another group's or customer's run).
          - 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; 429 RATE_LIMITED; 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>",
      "runId": "<runId>"
    },
    "name": "scrapewise_get_matcher_run_pairs"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe group's id.
kindNoMATCH | REVIEW.
pageNothe page, starting at 0.
sizeNopairs per page, 1 to 500.
runIdYesthe run's id (runId from scrapewise_get_matcher_history).
customerRefNoAdmin keys in Take Over only: the customerUniqueRef of the customer the admin works for. Required then; leave it out otherwise.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / id / description
      Added value: +"the group's id."
    • addedInput schema / properties / kind / description
      Added value: +"MATCH | REVIEW."
    • addedInput schema / properties / page / description
      Added value: +"the page, starting at 0."
    • addedInput schema / properties / runId / description
      Added value: +"the run's id (runId from scrapewise_get_matcher_history)."
    • addedInput schema / properties / size / description
      Added value: +"pairs per page, 1 to 500."
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description adds genuinely new context: 'costs nothing', a Read key suffices, and the ledgerStatus outcomes (COMPLETE/TRUNCATED/PARTIAL/NONE) including that older runs keep no pair list and return empty content. It also documents the Take Over precondition for customerRef. It stops short of describing pair ordering guarantees or how truncation is repaired.

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 what the tool does and when to use it, then Args/Returns/Examples/Error Handling in a predictable order. The Args block largely restates a schema that is already 100% described, so a few lines are redundant, but nothing is confusing.

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?

No output schema exists and the runtime hint warns the payload is dynamic, so the Returns block carries the burden well: it enumerates the envelope fields, explains each ledgerStatus state, and lists per-pair fields (sourceIdentity, masterRef, decision, score, matchOrigin). Combined with the documented error codes, an agent can call and interpret this correctly.

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; the description earns a step up by supplying defaults the schema omits (kind=MATCH, page=0, size=100), the 1-500 bound with its error code, and the precise Take Over condition where customerRef becomes required (409 TAKE_OVER_ACTIVE otherwise). It also ties runId to its source field in scrapewise_get_matcher_history.

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 product pairs one finished matching run found, split by kind (MATCH vs REVIEW), in the run's own order, capped at 500 per page. It also disambiguates from siblings by naming scrapewise_get_match_evidence for current matches and scrapewise_get_matcher_history for the run list.

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?

The Examples section gives explicit 'Use when' phrasings ('which matches did last week's run have?') and a 'Don't use when' clause routing to two named alternatives. There is also a stated edge condition: it is for older runs, even after a newer run replaced their matches.

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.