Skip to main content
Glama

scrapewise_delete_scraper_group_price_monitor_pick

DestructiveIdempotent
        Removes the stored answer for one pairing-column value, so the comparison goes back to
        reporting that it cannot identify our listing there.

        Carries a BODY, which is unusual for DELETE and deliberate: the key is customer text and
        must not become a path segment — see PUT .../pick.

        Removing an answer that was never given SUCCEEDS. The customer's intent is "nothing should
        be pinned here", and afterwards nothing is; a 404 would only prompt the portal to alarm
        about a state the customer already wanted.

        Args:
          - id (string, path param, required): the group's MongoDB ObjectId.
          - body (GroupPickKeyDTO, required): key — the pairing-column value to un-pin.

        Returns:
          The group's full pick map after the removal, same shape as GET .../picks.

        Examples:
          - Use when: "that is not the one we sell after all" on EAN 4741243009332.
          - Don't use when: you want to clear every pick because the pairing column moved — the
            portal re-reads the picks itself after such a change; there is no bulk clear.

        Error Handling:
          - 400 (CustomerError envelope) if no group with the given id exists for this customer.
          - 400 if key is blank or longer than 512 characters.
          - 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>",
      "body": "<body>"
    },
    "name": "scrapewise_delete_scraper_group_price_monitor_pick"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe group's MongoDB ObjectId.
bodyYesIdentifies the pick to remove, by its pairing-column value.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / id / description
      Added value: +"the group's MongoDB ObjectId."
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: explains why a DELETE carries a body (customer text must not become a path segment), why deleting a non-existent pick succeeds (matching idempotentHint and destructiveHint semantics), and what the response contains. Error codes and their meanings are enumerated.

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 action, then organized into rationale, args, returns, examples, and error handling with zero filler content. It is longer than strictly necessary, and the embedded rationale about portal alarms could be trimmed, but each section carries distinct actionable information.

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?

Covers everything an agent needs for a destructive, idempotent mutation: required body, idempotent delete semantics, returned pick map shape, and full error taxonomy. The absence of an output schema is compensated by stating the return mirrors GET .../picks.

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: 'key' is customer-supplied text requiring body placement rather than a path segment, and 'id' identifies the group's MongoDB ObjectId. Length limits are covered by the schema and reinforced in error handling.

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 the stored answer for one pairing-column value, restoring the 'cannot identify our listing' state. It also contrasts with the PUT .../pick counterpart, so the agent can distinguish write directions without opening another schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit 'Use when' and 'Don't use when' sections give a concrete scenario (un-pin an EAN after discovering it's not the sold item) and an exclusion (no bulk clear when the pairing column moves). The exclusion is slightly indirect because it points at portal behavior rather than naming a sibling tool, but the guidance is clear.

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.