Skip to main content
Glama

scrapewise_get_matcher_review_pairs

Read-onlyIdempotent
        Returns the product pairs of a group's Review tab by id, up to 500 per call, with their scores and, when
        asked, chosen columns of both products. Read-only; costs nothing; a Read key may call it. Get the ids from
        scrapewise_get_matcher_review_ids first (sort=ai for the AI first review order).

        Args:
          - id (string, path, required): the group's id.
          - configId (string, path, required): the review key of the group's matching setup.
          - body (required): ids (1 to 500 pair ids); optional fields, leftFields, rightFields (column names to
            show for the product and the main-list row, at most 40 each).
          - 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.

        Returns:
          One entry per pair found: id, stablePairKey, matcherRunId, leftKey, rightKey, picture links, scores
          (textScore, imageCosine, picScore, fusionScore, numberScore), status, the chosen columns (leftFields,
          rightFields), lines and stepScores on newer-engine groups, and aiReview when the AI first review has
          looked at the pair in the current run: status (done, pending, failed, invalid, skipped), and for done
          verdict (SAME, DIFFERENT, UNSURE), matchProbability (0 to 1), reason (at most 25 words), agreeing lines
          and conflicting values, each named by the setup's line key and its columns; photoText when it read the
          photos. aiReview is advice only: it never changes a match. An unknown or foreign id is left out.

        Examples:
          - Use when: "show me the first 20 pairs to review and what the AI thinks" -> ids from review ids.
          - Don't use when: you want to save a decision -> the portal Review tab.

        Error Handling:
          - 400: no ids, more than 500 ids or more than 40 fields.
          - 404: unknown group, another customer's group or a configId that is not this group's.
          - 409 TAKE_OVER_ACTIVE: 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>",
      "configId": "<configId>",
      "body": "<body>"
    },
    "name": "scrapewise_get_matcher_review_pairs"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe group's id.
bodyYesids (1 to 500 pair ids); optional fields, leftFields, rightFields (column names to show for the product and the main-list row, at most 40 each).
configIdYesthe review key of the group's matching setup.
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. Changed3 schema fields changed
    • addedInput schema / properties / body / description
      Added value: +"ids (1 to 500 pair ids); optional fields, leftFields, rightFields (column names to show for the product and the main-list row, at most 40 each)."
    • addedInput schema / properties / configId / description
      Added value: +"the review key of the group's matching setup."
    • addedInput schema / properties / id / description
      Added value: +"the group's id."
  2. Added

TDQS

A4.8/5.0
Behavior5/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 real context: 'costs nothing', a Read key suffices, unknown or foreign ids are silently omitted, and aiReview is advice only and never changes a match. It also enumerates error codes including 409 TAKE_OVER_ACTIVE and the customerRef remedy.

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. It is somewhat long and repeats schema constraints (500 ids, 40 fields), but every section carries useful 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?

No output schema exists, but the Returns section fully documents the response shape including scores, status, chosen columns, stepScores, and the aiReview sub-object with its verdicts and probability range. Combined with error handling, an agent has everything needed to call and interpret it.

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 beyond the schema: leftFields/rightFields are explained as columns for the product and the main-list row, and customerRef is scoped to admin Take Over. The 1-to-500 id bound and 40-field cap are restated rather than new, keeping it just below a 5.

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: returns the product pairs of a group's Review tab by id, up to 500 per call, with scores and optionally chosen columns. It is clearly distinguishable from the sibling scrapewise_get_matcher_review_ids, which supplies the ids this tool consumes.

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?

Explicitly routes the agent: 'Get the ids from scrapewise_get_matcher_review_ids first (sort=ai for the AI first review order)' and provides a 'Use when' / 'Don't use when' pair that names the alternative (the portal Review tab) for saving decisions.

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.