Skip to main content
Glama

scrapewise_update_scraper_group_data_quality

Idempotent
        Sets the group-level overrides of the engine data-quality behaviours. Each field
        is tri-state: true = force ON for this group, false = force OFF, null = inherit the
        global engine flag (the default for every group). All fields are applied as sent.

        Group-scoped because these behaviours are INTENT declarations: a group that tracks one
        product per address (EAN-keyed price tracking) wants the one-row collapse; a group that
        scrapes category listings must never get it. The page cannot tell these intents apart —
        the group config can.

        Args:
          - id (string, path param, required): the group's MongoDB ObjectId.
          - body (GroupDataQualityDTO, required): the nullable overrides —
            singleProductRowSelectOverride (at most one saved row per SINGLE_PRODUCT address),
            sitemapSingleUrlPerGtinTitleOverride (one sitemap url per EAN-shaped title),
            priceProductCodeGuardOverride (drop a price that is provably the product's own
            item code), ldJsonAvailabilityBackfillOverride (fill a missing availability from
            the page's JSON-LD offers.availability). Each true/false/null; null = inherit the
            global engine flag.

        Returns:
          The updated GroupDTO (carrying the override fields alongside the usual
          name/schedule/retention fields).

        Examples:
          - Use when: "this group tracks one product per EAN-keyed address (price tracking)
            and must collapse related-product noise" → set all overrides true.
          - Use when: "this group scrapes category listings and must never lose rows" →
            set singleProductRowSelectOverride false (or null when the global is already off).
          - Don't use when: you want to change the platform-wide defaults → those live in
            the admin system settings (scraperEngine flags), not on a group.

        Error Handling:
          - 400 (CustomerError envelope) if no group with the given id exists for this customer.
          - 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_data_quality"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe group's MongoDB ObjectId.
bodyYesGroup-level data-quality overrides; null = inherit the global engine flag.

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.8/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the tri-state contract (true = force ON, false = force OFF, null = inherit the global flag, which is the default) and that "all fields are applied as sent." It also names the return value (updated GroupDTO) and error envelopes (400 CustomerError when the group does not exist for this customer, 401, 500).

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?

Well front-loaded: purpose, scope rationale, then mechanics, then examples and errors. The Args section largely restates schema descriptions that are already at 100% coverage, which is some duplicated payload, but the intent narrative and tri-state rule earn their space.

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 nested-body mutation with no output schema, the description covers what is written, the null-inherit default, the replacement semantics, error cases, and what comes back. Nothing an agent needs in order to invoke it correctly is missing.

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 already 100%, and the description still adds semantic value by explaining what several overrides actually change in the engine (one saved row per SINGLE_PRODUCT address, one sitemap url per EAN-shaped title, dropping a price that is the product's own item code, JSON-LD availability backfill). It documents only a subset of the ten body fields, leaving the rest to the schema, so it is strong but not exhaustive.

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: "Sets the group-level overrides of the engine data-quality behaviours." It immediately scopes the operation to a group (via the path id) and explicitly contrasts it with platform-wide engine flags, so an agent can tell it apart from update tools that write global defaults.

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?

Has explicit "Use when" scenarios (EAN-keyed price tracking vs. category listings) and an explicit "Don't use when" that redirects to admin system settings for platform-wide defaults. The intent rationale — the page cannot distinguish these intents, the group config can — tells the agent why group scope is the right lever.

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.