Skip to main content
Glama
Sign In

Scrapewise

by ai.scrapewise
OverviewDiscussionsAdmin

scrapewise_get_scraper_shared_group_list

Read-onlyIdempotent
        Returns groups owned by other customers that have been shared to this
        customer (read access). Distinct from scrapewise_get_scraper_group_list which
        returns this customer's OWN groups. Use to discover groups the customer can
        read but not modify — these groups appear alongside owned groups in the
        customer's UI but mutation calls (delete, create-scraper, schedule-change)
        against them will 400 with an ownership error from the service layer.
        Returned shape matches the owned-groups DTO so a single UI rendering path
        handles both.

        Args:
          (none — endpoint is parameter-free.)

        Returns:
          `List<GroupDTO>` — same shape as own-groups; empty list if nothing is
          shared to this customer. Each entry's `customerRef` field reveals the
          owning customer's `customerUniqueRef` (so the agent can disambiguate
          identically-named groups across share boundaries).

        Examples:
          - Use when: "what shared groups can I read?"
          - Use when: building a "shared with me" tab in the dashboard
          - Don't use when: you want your own groups → use
            scrapewise_get_scraper_group_list (separate surface)

        Error Handling:
          - 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_shared_group_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, yet the description still adds real behavior: reads succeed but mutation calls (delete, create-scraper, schedule-change) against these groups fail with a 400 ownership error, the result is an empty list when nothing is shared, and failure modes are 401/500. That is materially more than the annotations convey.

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 ownership distinction before the supporting detail, and the Examples/Error Handling sections are scannable. Slightly redundant — the "Don't use when" line restates the sibling split already made in the first sentence, and the Args block is filler for a zero-param endpoint.

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?

Covers return shape, empty-list case, the customerRef disambiguation field, and error codes, which is appropriate given no output schema exists. Minor tension: it promises a concrete List<GroupDTO> shape while the runtime hint warns the response is a dynamic blob to be parsed defensively, so the agent should not treat the DTO fields as guaranteed.

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?

Zero parameters, so the baseline is 4 and the description only confirms "none — endpoint is parameter-free," which adds no meaning beyond the empty schema. There is nothing further it could reasonably document here.

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 groups owned by other customers that have been shared to this customer") and immediately contrasts it with the sibling that returns the customer's own groups. An agent can pick between the two 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 positive triggers ("what shared groups can I read?", building a 'shared with me' tab) and an explicit negative trigger with the named alternative ("Don't use when: you want your own groups → use scrapewise_get_scraper_group_list"). Both sides of the routing decision are covered.

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

All Scrapewise toolsInspect
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.

Resources