Scrapewise

scrapewise_get_scraper_load_history

Read-onlyIdempotent

        Returns the paginated history of all scraper runs (scraperJobStatus records)
        for the customer. Each record represents one execution attempt of a scraper:
        scraper id, group id, state (PENDING / RUNNING / COMPLETED / FAILED / STOPPED),
        started + finished timestamps, link counts, error counts. Filter via the
        `filters` JSON to narrow by groupId, scraperId, state, or date range.

        Args:
          - filters (string, query param, optional): URL-encoded JSON object. Common
            keys: `groupId`, `scraperId`, `state`. Pass empty for all customer runs.
          - groupId (string, query param, optional): the same narrowing as
            `filters={"groupId":"..."}`, spelled as a plain parameter. Given both, the
            explicit parameter wins. Absent, the whole account's runs come back.
          - scraperId (string, query param, optional): as `groupId`, for one automation.
          - withDeleted (boolean, query param, optional, default false): include
            soft-deleted runs in the result.
          - pageable (Spring Pageable): page, size, sort. Default sort: started DESC.

        Returns:
          Spring Page<ScraperJobStatusDTO> — `{content, totalElements, totalPages, ...}`.
          Each record carries id, scraperId, groupId, state, started, finished,
          successLinks, errorLinks, launchedByCustomer (boolean: did this customer
          start the run, or did the group's owning customer in a shared-group setup).

        Examples:
          - Use when: "show recent runs for scraper {id}" → filters={"scraperId":"..."}
          - Use when: "any failed runs in group {id}?" → filters={"groupId":"...","state":"FAILED"}
          - Use when: "what state is the most-recent run in?" → page=0, size=1
          - Don't use when: you want THIS scraper's lastRunState only →
            read scrapewise_get_scraper.lastRunState (cheaper)

        Error Handling:
          - 400 if filters JSON is malformed.
          - 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "scrapewise_get_scraper_load_history"
  }
}

Input Schema

Name	Required	Description
`id`	No
`page`	No	Zero-based page index (0..N)
`size`	No	The size of the page to be returned
`sort`	No	Sorting criteria in the format: property,(asc\|desc). Default sort order is ascending. Multiple sort criteria are supported.
`filters`	No
`groupId`	No
`scraperId`	No
`withDeleted`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), but the description goes well beyond them: it lists the state enum, states the withDeleted default of false, the default sort of started DESC, the explicit-parameter-wins precedence, and the 400/401/500 error paths. The only soft spot is the Returns section, which promises specific DTO fields while the runtime hint warns the shape is dynamic — an agent reading both gets slightly mixed signals.

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?

The Args/Returns/Examples/Error Handling structure is front-loaded and scannable, and most sentences carry information an agent needs. It is on the long side, and the enumerated DTO field list somewhat duplicates what the runtime hint says cannot be relied upon.

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 an 8-parameter, zero-required tool with no output schema, the definition covers filtering, defaults, ordering, precedence, return envelope, and failure modes — nearly everything needed to call it correctly. The unexplained `id` parameter and the mismatch between the promised DTO fields and the dynamic response shape are the remaining gaps.

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?

With only 38% schema coverage this description does most of the work: it explains the URL-encoded JSON `filters` object and its common keys, the equivalence and precedence between filters and the plain groupId/scraperId parameters, the withDeleted default, and the pageable page/size/sort usage. The notable omission is the `id` parameter, which appears in the schema but is never mentioned in the description.

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 opening sentence names a specific verb and resource — 'Returns the paginated history of all scraper runs (scraperJobStatus records) for the customer' — and enumerates the fields each record carries. It also explicitly distinguishes itself from the cheaper scrapewise_get_scraper.lastRunState alternative, so an agent can pick it out without inspecting 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 three concrete 'Use when' scenarios mapped to actual query shapes (scraperId filter, groupId+state=FAILED, page=0/size=1) and one explicit 'Don't use when' that routes to a named sibling. There is also a precedence rule for when filters and explicit parameters are both supplied.

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.