Skip to main content
Glama

scrapewise_update_scraper_fallback

Idempotent
        Attaches a fallback scraper configuration to a SINGLE_PRODUCT scraper. The
        fallback runs automatically when the primary scraper extracts no data for a
        link — typically a backup parser for a sub-set of the same site or a different
        extraction strategy. Requires the FALLBACK_SCRAPER plan feature.

        Args:
          - body (FallbackScraperCreateDTO, required):
            - scraperId (string): id of the SINGLE_PRODUCT scraper to attach the
              fallback to.
            - fallback (ScraperDTO): the fallback scraper's configuration.

        Returns:
          The persisted ScraperDTO of the fallback (with id assigned), or null if the
          attachment failed silently (rare; usually 4xx instead).

        Examples:
          - Use when: "give scraper {id} a fallback that uses JSON-LD instead of CSS"
          - Don't use when: the primary scraper is MULTIPLE_PRODUCTS — fallbacks are
            SINGLE_PRODUCT-only

        Error Handling:
          - 402 if customer plan lacks FALLBACK_SCRAPER feature.
          - 400 if the primary scraper is not SINGLE_PRODUCT type.
          - 400 (CustomerError envelope) if scraperId doesn't exist 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": {
      "body": "<body>"
    },
    "name": "scrapewise_update_scraper_fallback"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesObject with the fields scraperId, fallback.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / body / description
      Added value: +"Object with the fields scraperId, fallback."
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, idempotentHint=true, destructiveHint=false; the description adds substantially beyond that: the plan-gate requirement, the automatic invocation behavior of the fallback, the rare null-return case, and a full error map (402 plan missing, 400 wrong scraper type, 400 unknown scraperId, 401). The runtime hint also warns the response is a dynamic string-or-object blob.

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 and sectioned (purpose, Args, Returns, Examples, Error Handling), so the agent can skim to the needed part. It is somewhat longer than necessary and the Args section duplicates schema-type information, but nothing is filler.

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 tool with no output schema, the description covers the prerequisite, the return value, the silent-failure edge case, and all error codes, plus the runtime warning about a dynamic response. Nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description spells out the meaning of scraperId and fallback (ScraperDTO) and notes fallback's structure is a full scraper config, which adds value. However, it conflicts with the input schema, which declares required fields scraperId and url while the description describes scraperId and fallback — an agent reading both gets contradictory guidance on what must be supplied. With 100% schema coverage the baseline would be 3, and the mismatch prevents going higher.

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 description opens with a specific verb and resource ('Attaches a fallback scraper configuration to a SINGLE_PRODUCT scraper') and immediately explains the runtime semantics of what a fallback is. It clearly separates this tool from the family of scrapewise_update_scraper_group_* / schema update siblings, which configure other parts of a scraper.

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?

Explicit 'Use when' and 'Don't use when' examples are given, plus a hard eligibility constraint (SINGLE_PRODUCT-only) and a plan prerequisite (FALLBACK_SCRAPER). An agent knows both the trigger scenario and the exclusion without inferring anything.

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.