Skip to main content
Glama

scrapewise_get_matcher_review_ids

Read-onlyIdempotent
        Lists the product pairs of a group's matching that still wait for a person's decision (the Review tab),
        as ids in the chosen order, optionally one page at a time. Read-only; costs nothing; a Read key may call it.
        Fetch the pairs themselves with scrapewise_get_matcher_review_pairs.

        Args:
          - id (string, path, required): the group's id.
          - configId (string, path, required): the review key of the group's matching setup
            (masterData.configId from scrapewise_get_matcher_job).
          - sort (string, query, optional, default total): total = the matcher's total score, highest first; name =
            the name score; photo = the photo score; desc = the photo description score; step1..step5 = one step's
            score (newer engine); ai = the AI first review order: pairs the AI has checked first, most likely the
            same product first, then the rest in total order (needs the AI review switched on for the group; without
            it the order is total). Case-insensitive; unscored pairs come last.
          - sources (string, query, optional): comma list of up to 100 source scraper ids; only their pairs.
          - offset, limit (integer, query, optional): one page of the list (limit 1 to 10000) plus total.
          - 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:
          snapshotTs, ids (pair ids in order), keys (the stable pair keys, same order), total (paged calls only),
          steps (newer-engine groups: the configured steps and their lines).

        Examples:
          - Use when: "which pairs of group {id} should I check first?" -> sort=ai, limit=20.
          - Use when: walking the whole review list page by page -> offset/limit.
          - Don't use when: you want why pairs matched -> scrapewise_get_match_evidence.

        Error Handling:
          - 400: an unknown sort, a bad sources value or a bad offset / limit.
          - 404: unknown group, another customer's group or a configId that is not this group's.
          - 409: the list cannot be filtered by source right now (show all, retry shortly); TAKE_OVER_ACTIVE.
          - 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>"
    },
    "name": "scrapewise_get_matcher_review_ids"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe group's id.
sortNototal (default), name, photo, desc, step1..step5 or ai (the AI first review order)
limitNoPage size, 1 to 10000; absent with no offset = the whole list
offsetNoPage start in the not-yet-decided list (0 or more); with limit
sourcesNoComma-separated source scraper ids (24-hex, at most 100) to focus on
configIdYesthe review key of the group's matching setup (masterData.configId from scrapewise_get_matcher_job).
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. Changed2 schema fields changed
    • addedInput schema / properties / configId / description
      Added value: +"the review key of the group's matching setup (masterData.configId from scrapewise_get_matcher_job)."
    • addedInput schema / properties / id / description
      Added value: +"the group's id."
  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, and the description layers on meaningful context: it costs nothing, a Read key suffices, offending sort/sources/offset values produce 400, unknown or cross-customer groups produce 404, and a 409 covers source-filter unavailability and TAKE_OVER_ACTIVE. It does not spell out ordering of the returned keys beyond the sort note, but the disclosure is well beyond the annotation baseline.

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 summary sentence, then structured Args/Returns/Examples/Error Handling sections that are easy to scan. The Args block largely duplicates the 100%-covered schema, which is some wasted length, but nothing is misleading or filler.

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?

With no output schema and a dynamic text-blob response, the definition compensates by documenting the returned fields (snapshotTs, ids, keys, total, steps) and noting total appears only on paged calls. Combined with the enumerated error codes and auth/cost notes, an agent has everything needed to call it 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 baseline is 3, but the description adds real semantics: sort values are explained behaviorally (total = matcher total score highest first, step1..step5 = one step's score, ai = AI-checked pairs then the rest in total order, case-insensitive, unscored last), and customerRef is scoped to admin Take Over use. sources and offset/limit mostly restate the schema.

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 pair ids still awaiting a human decision in the Review tab, in the chosen order, optionally paged — and explicitly routes to scrapewise_get_matcher_review_pairs for the pairs themselves. An agent can distinguish this from its closest sibling without opening either 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 explicit 'Use when' cases (sort=ai to prioritize, offset/limit to walk the list) and a 'Don't use when' redirect to scrapewise_get_match_evidence for match reasoning. The prerequisite that ai sort requires AI review to be switched on is also called 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.