Skip to main content
Glama

scrapewise_update_scraper_shared_group

Idempotent
        Grants read access on the given group to a list of other customers identified
        by email. Idempotent — re-sharing to the same email is a no-op. Subject to the
        DATA_SHARING plan feature; total shares per group capped by DATA_SHARING_LIMITS.

        Args:
          - id (string, path param, required): the group's MongoDB ObjectId.
          - body (List<SharedDTO>, required, non-empty): list of share targets, each
            with the recipient's email and (optionally) a permission flag.

        Returns:
          204 No Content.

        Examples:
          - Use when: "share group {id} with alice@example.com and bob@example.com"
          - Don't use when: you want to UNSHARE → use scrapewise_stop_scraper_shared_group

        Error Handling:
          - 402 if customer plan lacks DATA_SHARING feature.
          - 402 if total shares would exceed DATA_SHARING_LIMITS.
          - 400 if body is empty.
          - 400 (CustomerError envelope) if no group with the given id exists for this customer.
          - 401 Unauthorized.

[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>",
      "body": "<body>"
    },
    "name": "scrapewise_update_scraper_shared_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe group's MongoDB ObjectId.
bodyYeslist of share targets, each with the recipient's email and (optionally) a permission flag.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / body / description
      Added value: +"list of share targets, each with the recipient's email and (optionally) a permission flag."
    • addedInput schema / properties / id / description
      Added value: +"the group's MongoDB ObjectId."
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

Substantial context beyond the annotations: it discloses plan-feature gating (DATA_SHARING), share caps (DATA_SHARING_LIMITS), the 204 return, and specific failure codes (402 for plan/cap, 400 for empty body, 400 CustomerError for unknown id, 401). One shortfall: the description frames the operation purely as granting 'read access', while the schema exposes edit-rights flags (hasConfigEditRights, hasFiltersEditRights, hasScraperRunningRights), so the effect surface is understated.

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 purpose is front-loaded in sentence one, then organized into Args / Returns / Examples / Error Handling, which is easy to scan. It is a bit heavier than necessary — idempotency is asserted in the prose when the annotation already declares idempotentHint=true, and the restated Args duplicate a schema at 100% coverage.

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?

For a two-parameter mutation with no output schema, everything an agent needs is present: the 204 empty response, the plan and cap preconditions, the empty-body constraint, and a full status-code table. The runtime hint about a defensive JSON-as-text parse covers the remaining return-shape ambiguity.

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; the description adds real value by stating body must be non-empty (the schema sets no minItems) and by tying that constraint to the 400 error. It loses a point for describing the body as carrying 'a permission flag' in the singular when the schema actually defines three distinct boolean rights.

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 first sentence gives a specific verb ('Grants read access'), a specific resource ('the given group') and a specific target set ('a list of other customers identified by email'). It is immediately distinguishable from the unshare sibling, which is named later.

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?

The Examples block states both directions explicitly: 'Use when: share group {id} with alice@...' and 'Don't use when: you want to UNSHARE → use scrapewise_stop_scraper_shared_group'. The alternative tool is named rather than 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.