Skip to main content
Glama

scrapewise_get_matcher_scope_jobs

Read-onlyIdempotent
        Lists the scraper runs of the group that a matching save may use as its scope: the newest
        finished run per scraper of the group. Read-only; costs nothing. These run ids are what the scope
        list (and the matchersByScope keys) of scrapewise_update_matcher_job take.

        Args:
          - id (string, path, required): the group's id.
          - masterJobId (string, query, optional): the run used as the main list; it is left out of the
            answer, so the main list is never matched against itself.
          - 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 ScraperJobStatusDTO (id = the run id, scraperId, scraperName, state, finished,
          itemsQuantity), newest first.

        Examples:
          - Use when: "which runs can I match in group {id}?" before a save.
          - Use when: refreshing a setup to the newest runs of the same scrapers.
          - Don't use when: you need an older run of one scraper -> scrapewise_get_scraper_load_history
            (filter by scraper) and pass that run id in scope.

        Error Handling:
          - 400 (CustomerError): no group with this id for this customer, or a bad masterJobId.
          - 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_scope_jobs"
  }
}

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.
masterJobIdNothe run used as the main list; it is left out of the answer, so the main list is never matched against itself.

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 / masterJobId / description
      Added value: +"the run used as the main list; it is left out of the answer, so the main list is never matched against itself."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description adds cost ('costs nothing'), the exclusion behavior of masterJobId (the main list is never matched against itself), and a concrete error profile (400 CustomerError, 409 TAKE_OVER_ACTIVE, 401, 500) with the remediation path for Take Over. No contradiction with the annotations.

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?

Purpose and read-only/cost facts are front-loaded, and the Examples and Error Handling sections earn their space. The Args block mostly repeats a schema that is already at 100% coverage, which is avoidable duplication.

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?

For a 3-parameter read tool with no output schema, the description supplies return shape, field list, ordering (newest first), and error handling. The one gap is that it does not mention the dynamic/JSON-as-text nature of the response flagged by the runtime hint, so an agent could over-trust the listed DTO fields.

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 a 3 baseline applies, but the description goes further by tying customerRef to a specific failure mode (409 TAKE_OVER_ACTIVE without it) and explaining the consequence of masterJobId rather than only restating its type. The Args section largely mirrors the schema, which caps it below 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?

The first sentence states a precise verb and resource: it lists the newest finished run per scraper of a group, and immediately explains what those ids are consumed by ('the scope list ... of scrapewise_update_matcher_job'). A sibling is named in the 'Don't use when' clause, so the agent can distinguish this from scrapewise_get_scraper_load_history 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?

Explicit when-to-use cases are given ('before a save', 'refreshing a setup to the newest runs of the same scrapers') plus an explicit exclusion routing to scrapewise_get_scraper_load_history when an older run is needed. This is the full when/when-not/alternative pattern.

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.