Skip to main content
Glama

scrapewise_stop_scraper_shared_group

DestructiveIdempotent
        Removes a single share entry — the recipient identified by email loses read
        access to the group. NOT idempotent: revoking a share that doesn't exist (or
        an email that was never shared with) errors with 400 (CustomerError envelope:
        "Customer X group Y is not shared with customer Z"). Other recipients are
        unaffected. Check current shares via scrapewise_list_scraper_shared_group_list
        before revoking.

        Args:
          - id (string, path param, required): the group's MongoDB ObjectId.
          - email (string, query param, required): the recipient's email to revoke.

        Returns:
          204 No Content.

        Examples:
          - Use when: "remove alice@example.com from group {id}"
          - Don't use when: you want to revoke ALL shares → call this once per email
            (no batch revoke API)

        Error Handling:
          - 400 (CustomerError envelope) if no group with the given id exists for this
            customer, OR if the caller is not the group's owner, OR if the email was
            never shared with on this group.
          - 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>",
      "email": "<email>"
    },
    "name": "scrapewise_stop_scraper_shared_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe group's MongoDB ObjectId.
emailYesthe recipient's email to revoke.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / email / description
      Added value: +"the recipient's email to revoke."
    • addedInput schema / properties / id / description
      Added value: +"the group's MongoDB ObjectId."
  2. Added

TDQS

A4/5.0
Behavior1/5

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

The description declares "NOT idempotent" and specifies that revoking a non-existent share returns a 400 CustomerError, but the annotations set idempotentHint=true. These are directly contradictory statements about retry behavior, which is exactly the trait an agent relies on to decide whether a failed call can be safely repeated. Despite otherwise rich error-envelope detail, the conflict with structured data forces a 1.

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 effect and the non-idempotency warning, then structured into Args/Returns/Examples/Error Handling sections. Slightly long for a two-parameter tool and the Args section largely restates the schema, but every block is scannable and the critical caveats appear first.

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?

No output schema exists, but the description covers the return (204 No Content) and enumerates the 400/401/500 failure modes including the ownership and never-shared cases. For a destructive two-parameter mutation, an agent has everything needed to call it and interpret failures.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it identifies id as a path parameter, email as a query parameter, and ties each to its semantic role (the group to modify vs. the recipient whose read access is revoked). That goes beyond the terse schema descriptions.

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 — removes a single share entry so the identified recipient loses read access — and immediately distinguishes the scope from a group-wide revoke by noting other recipients are unaffected. An agent can tell this apart from the delete/stop group siblings without opening their schemas.

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 an explicit positive trigger ("remove alice@example.com from group {id}"), an explicit exclusion (don't use when you want to revoke ALL shares — call once per email, no batch API), and names the sibling to consult first (scrapewise_list_scraper_shared_group_list). This is the strongest form of routing guidance.

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.