Skip to main content
Glama

scrapewise_update_scraper_group_price_monitor

Idempotent
        Records which scraper in the group is the customer's OWN, how a row is paired with a
        competitor's row, and which columns hold the price and the product label. All fields are
        applied as sent; null clears that one choice back to "let the portal auto-pick".

        Group-scoped rather than per-user because this describes the group's DATA, not a personal
        preference: a group is one collection with its own customer-defined column names, and the
        answer to "which column is the price" is the same answer for every colleague. Kept in
        browser storage it was per-person, so two people could open one group and be shown two
        different prices for the same product.

        Args:
          - id (string, path param, required): the group's MongoDB ObjectId.
          - body (GroupPriceMonitorDTO, required): me (the scraper NAME the customer owns),
            mode ("matched" = product-matcher output, "title" = identical column value), key
            (the column paired on when mode is not "matched"), price, productName, category
            (top-level category column), subcategory, salePrice (discounted price shown
            alongside price). Each nullable; null = auto-pick. `confirmedAt` in the body is
            IGNORED — the server stamps it, because saving is what confirms. A column cannot
            be reused across two of these roles (400 if it is).

        Returns:
          The updated GroupDTO, carrying priceMonitor with the server-stamped confirmedAt.

        Examples:
          - Use when: "in group {id} we are the scraper 'home4you', pair products on identical
            `kood`, and the price is `hind`".
          - Use when: "stop forcing a price column in group {id}, go back to auto" → price=null.
          - Don't use when: you want to change a personal view/sort/filter — those are not
            group data and are not stored here.

        Error Handling:
          - 400 (CustomerError envelope) if no group with the given id exists for this customer,
            or if two of the settings name the same column.
          - 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_update_scraper_group_price_monitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe group's MongoDB ObjectId.
bodyYesHow a group's rows are read as a price comparison; null = portal auto-picks.

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.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description still earns credit beyond that: it discloses that null clears a single role back to auto-pick, that body.confirmedAt is ignored because the server stamps it, that a column reused across two roles produces a 400, and it documents 400/401/500 handling plus the returned GroupDTO. Return-shape caveats are supplied by the runtime hint rather than the description, which keeps this from the top band.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Structure is front-loaded and scannable, with Args/Returns/Examples/Error Handling headings, but the Args block largely restates a schema that is already 100% described. The multi-sentence rationale about browser storage versus group storage is explanatory background rather than invocation guidance, so the definition runs longer than the decision-relevant content requires.

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 a nested DTO, the definition covers what is written, the null-to-auto semantics, the server-stamped field, the conflict rule, the error envelope on missing group, and the return value. The absence of an output schema is compensated by naming the returned GroupDTO and its priceMonitor.confirmedAt field.

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 description coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: mode is glossed as 'matched' = product-matcher output vs 'title' = identical column value, and the cross-field invariant ('A column cannot be reused across two of these roles, 400 if it is') is a constraint no single property description conveys. The 'which column is the price is the same answer for every colleague' framing clarifies why these are group-level rather than per-user values.

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 opening sentence names a specific verb-and-resource pair: it records which scraper is the customer's own, how rows are paired with a competitor, and which columns hold price and product label. The second paragraph explicitly separates this from personal preferences and from the sibling anchor/pick operations by declaring the data 'group-scoped rather than per-user'. An agent can tell exactly what state this tool writes without opening the 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?

Usage is pinned down with two positive 'Use when' examples (setting scraper/column roles, and resetting to auto via price=null) and one explicit exclusion: 'Don't use when: you want to change a personal view/sort/filter — those are not group data and are not stored here.' The null-to-auto-pick convention gives a concrete alternative action for the teardown case.

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.