Scrapewise

scrapewise_get_group_delivery_status

Read-onlyIdempotent

        Tells whether a group's data for one day is complete: every scheduled feed scraped, the matching (or the
        daily price refresh) covers those scrapes, and - when the group keeps a daily matched file - that file is
        built. Read only, costs nothing, computed from job records (cached 15 seconds).

        Rules: a run counts for the day it finished in (a scrape that starts 23:50 and ends 01:00 belongs to the
        second day). Before the daily cut-off hour (admin setting, default 14:00 in the group's time zone) a feed
        that has not run yet is NOT_STARTED and the day is PENDING; at the cut-off it becomes FAILED (reason
        NOT_RUN) and a still-running feed PARTIAL (reason OVERDUE), so the day turns PARTIAL the same day. A feed
        with far fewer rows than its previous run is PARTIAL (reason ROW_DROP). STALE = nothing happened for many
        hours (admin setting, default 36).

        Args:
          - id (string, path, required): the group's id.
          - day (string, query, optional): YYYY-MM-DD in the group's time zone; default today. At most 366 days
            back.
          - customerRef (string, query, optional): only for a Scrapewise admin key while the admin works in
            another customer's account (Take Over): that customer's customerUniqueRef. Leave it out otherwise.

        Returns:
          {groupId, day, timezone, status: COMPLETE|PARTIAL|PENDING|STALE, complete, reasons[], scrapes: {expected,
          finished, partial, failed, running, notStarted, feeds[{scraperId, name, scheduled, runId, state, started,
          finished, rows, previousRows, verdict: OK|PARTIAL|FAILED|RUNNING|NOT_STARTED|NOT_DUE, reason}]}, master
          (the uploaded master file's last sync, when the matching master is a file), matching {configured, status,
          lastRunId, lastMatchedAt, coversScrapesUntil, hasNewData, coversDay, priceRefresh}, file {ready, formats,
          latestPath, ...} when the group keeps a daily file, webhook (no secret), cutoffAt, computedAt}.

        Examples:
          - Use when: "is today's data for group {id} complete?" or "which shop failed to scrape today?".
          - Use when: deciding whether to download today's matched file yet (file.ready, file.latestPath).
          - Don't use when: you need the rows themselves -> read the group's data or the matched-results file.

        Error Handling:
          - 400 INVALID_DAY: day is not YYYY-MM-DD or out of range; 400 (CustomerError): no group with this id for
            this customer.
          - 409 TAKE_OVER_ACTIVE: this key's admin works in another customer's account - send customerRef.
          - 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_group_delivery_status"
  }
}

Input Schema

Name	Required	Description
`id`	Yes
`day`	No	YYYY-MM-DD in the group's time zone; default today.
`customerRef`	No	Admin 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.

First observedNov 9, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds substantial context beyond them: computation from job records, a 15-second cache, day-boundary rules, cut-off behavior, NOT_STARTED/FAILED/PARTIAL/STALE semantics, row-drop detection, and overdue handling.

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?

Well structured into purpose, rules, args, returns, examples, and errors, with the core purpose front-loaded. It is dense and mostly justified by the tool's complexity, but some material repeats the schema or annotations and the Returns enumeration is long.

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?

There is no output schema, so the detailed Returns section is necessary and covers status values, scrape counts, matching/file/webhook context, cut-off and computation timestamps. Error handling and parameter constraints are also included, making the definition complete for a complex status tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 67% schema description coverage, the description supplies full meaning for all three parameters: id as the group id, day as YYYY-MM-DD in the group's time zone with today as default and a 366-day limit, and customerRef as an admin-only Take Over field. It adds constraints and context beyond 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?

Opens with a specific verb, resource, and scope: whether a group's data for one day is complete. It clearly distinguishes itself from data-reading siblings by telling the agent to read the group's data or matched-results file when rows are needed. An agent can select it without opening the 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' examples for checking daily completeness and deciding whether a matched file is ready, plus a 'Don't use when' case pointing to row-level data tools. The alternatives are described semantically, leaving little inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Scrapewise tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.