Skip to main content
Glama

scrapewise_list_scraper_shared_group_list

Read-onlyIdempotent
        Returns the recipient emails that have access to the given group via share.
        The owning customer is implicit (you must own the group to call this — the
        service layer 400s if you don't); other customers' shares of their own
        groups TO you can be discovered via scrapewise_get_scraper_shared_group_list
        instead. Use to audit a group's access list before granting / revoking, and
        to render an "X has access" UI section against a group detail page. Empty
        list means the group is not shared with anyone — only the owner can see it.

        Args:
          - id (string, path param, required): the group's MongoDB ObjectId.

        Returns:
          `List<string>` — the recipient emails. Empty list if not shared to anyone.
          Order is repository-natural (not alphabetical); sort client-side if you
          need stable display.

        Examples:
          - Use when: "who has access to group {id}?"
          - Use when: auditing a group's share list before revoking via
            scrapewise_stop_scraper_shared_group
          - Don't use when: you want to see groups shared TO you →
            use scrapewise_get_scraper_shared_group_list (separate surface)

        Error Handling:
          - 400 `INVALID_ID` if `id` is not a 24-character id. (Before 2026-09-22 a
            malformed id was answered HTTP 500 INTERNAL with a correlation id and no
            explanation — that was this seam, not a sharing problem.)
          - 400 (CustomerError envelope) if no group with the given id exists for
            this customer. A group that exists but is shared with nobody is NOT an
            error — it answers 200 with an empty list.
          - 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_list_scraper_shared_group_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the description adds real value beyond that with the ownership requirement (service layer 400s if you don't own the group), the empty-list semantics, and the fact that ordering is repository-natural rather than alphabetical. Error handling is enumerated per status code. The only shortfall is that the permissive/dynamic response caveat lives in a runtime hint rather than in the description proper.

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 core sentence and organized into Args/Returns/Examples/Error Handling, so scanning is easy. A few lines are incidental trivia (the pre-2026-09-22 HTTP 500 behavior), which is mild padding in an otherwise efficient definition.

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?

One required parameter, no output schema, and full annotation coverage — yet the description still supplies return shape (List<string> of emails), ordering caveat, empty-list meaning, and a complete error matrix. Nothing an agent needs to invoke or interpret the result is missing.

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 coverage is 0%, so the description must carry the parameter, and it does: it identifies `id` as a required path parameter holding the group's MongoDB ObjectId and specifies the 24-character format in the error section. That is enough to construct a valid call without consulting external docs.

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 and resource: "Returns the recipient emails that have access to the given group via share." It explicitly distinguishes this surface from scrapewise_get_scraper_shared_group_list, which covers the inverse direction, so an agent can pick correctly 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 concrete when-to-use cases (auditing before granting/revoking, rendering an "X has access" UI section) and an explicit "Don't use when" clause redirecting to the sibling for groups shared TO you. Nothing about tool selection is left to inference.

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.