Scrapewise

scrapewise_get_scraper_list

Read-onlyIdempotent

        Returns the customer's complete list of scrapers — every scraper they've configured,
        across all groups, in a flat list. Each entry has just identifying metadata
        (id, name, group reference, scraper type, last-run state) — not the full configuration.
        Use this as the starting point when you don't yet know which scraper the customer is
        referring to: list first to find the id, then call `scrapewise_get_scraper` for the
        full configuration of the one you want.

        Args:
          - groupId (string, query param, optional): return only the scrapers in this
            group. Absent, the whole account comes back, exactly as before. A group id
            that is not this customer's own matches nothing and returns an empty list —
            it is never an existence oracle for another account's groups.

        Returns:
          An array of scraper-summary objects: id, name, type, group reference, last-run
          state. Empty array if the customer has no scrapers configured.

        Examples:
          - Use when: "show me all my scrapers" → no args
          - Use when: "what's the id of the scraper called 'mototas'?" → call this then
              filter the result locally by name
          - Use when: "which scrapers are in group {id}?" → groupId={id}
          - Don't use when: you already have a scraper id → use scrapewise_get_scraper

        Error Handling:
          - 401 Unauthorized if no valid Authorization header is present.
          - 500 INTERNAL with correlationId on unexpected server error.

[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_list"
  }
}

Input Schema

Name	Required	Description	Default
`groupId`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

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, closed-world, non-destructive, so the safety profile is covered; the description adds genuinely new behavior: entries carry summary metadata only, not full config, and a groupId belonging to another account returns an empty list rather than acting as an existence oracle. It also documents 401 and 500-with-correlationId failure modes, which annotations cannot express.

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 purpose, then Args/Returns/Examples/Errors sections that each earn their place. There is mild redundancy — the groupId filtering rule appears in both Args and the examples, and the Returns section restates the field list already given in the opening paragraph.

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?

With no outputSchema, the description supplies the return shape, empty-list case, and error behavior, which is enough to call it correctly. Minor gap: it asserts a fixed array of scraper-summary objects while the runtime hint warns the response shape is dynamic and should be parsed defensively, so the two are slightly at odds.

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?

Schema description coverage is 0%, so the description must carry the lone parameter, and it does: groupId is optional, filters to a single group, absent means the whole account, and a foreign group id yields an empty list. That is meaning well beyond the bare `{"groupId": "string"}` 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: returns the customer's complete list of scrapers across all groups in a flat list, with identifying metadata only. It explicitly distinguishes itself from `scrapewise_get_scraper`, which returns full configuration for a single scraper, so an agent can choose between them 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?

Gives explicit when-to-use cases (all scrapers, resolving an id by name, listing a group) and an explicit don't-use case routing to `scrapewise_get_scraper` when an id is already known. The 'list first to find the id, then fetch the full config' workflow is spelled out rather than implied.

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.