Skip to main content
Glama

scrapewise_update_scraper_schema

Idempotent
        Binds this scraper to the given schema. For a CUSTOM schema, the supplied `schemaId`
        is a "which group" hint — the server always re-resolves it to that group's live-current
        latest version at write time, so the response's `schemaId` may differ from the request
        body if another save had already published a newer version of the group. Non-CUSTOM
        schemas resolve unchanged.

        Args:
          - id (string, path param, required): the scraper's MongoDB ObjectId.
          - body (AttachSchemaDTO, required): schemaId — any schema id belonging to this
            customer (or a global non-CUSTOM schema).

        Returns:
          The updated ScraperDTO (schemaId reflects the resolved binding).

        Examples:
          - Use when: "attach my Custom Schema {id} to scraper {id}"
          - Use when: "switch scraper {id} to schema {id}"

        Error Handling:
          - 400 (CustomerError envelope) if no scraper with the given id exists for this
            customer, or the schemaId does not resolve to any schema.
          - 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_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe scraper's MongoDB ObjectId.
bodyYesschemaId — any schema id belonging to this customer (or a global non-CUSTOM schema).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / body / description
      Added value: +"schemaId — any schema id belonging to this customer (or a global non-CUSTOM schema)."
    • addedInput schema / properties / id / description
      Added value: +"the scraper'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 (readOnlyHint=false, idempotentHint=true, destructiveHint=false) by disclosing the non-obvious write-time behavior: a CUSTOM schemaId is a 'which group' hint that the server re-resolves to the group's live-current version, so the returned schemaId may differ from the request. It also enumerates 400/401/500 failure conditions, which annotations do not cover.

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 and the resolution caveat, then structured into Args/Returns/Examples/Error Handling, so each block is scannable and purposeful. The CUSTOM-resolution paragraph is dense but carries real decision-relevant information, so the length is largely earned.

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 the argument contract, the resolution semantics an agent must anticipate, the returned DTO, concrete usage examples, and error envelopes — everything needed to invoke and interpret results despite no output schema. The note that responses are JSON-as-text with dynamic shape rounds out the picture.

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 already 100%, so the baseline is 3; the description earns above that by explaining that schemaId for CUSTOM schemas is only a group hint re-resolved server-side, and by noting it may be any schema id belonging to this customer or a global non-CUSTOM schema. It does not restate the id parameter beyond the schema's ObjectId note.

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 — 'Binds this scraper to the given schema' — and immediately clarifies the custom-vs-non-CUSTOM resolution semantics, which no sibling (e.g. update_scraper_group_*, update_matcher_job) covers. An agent can tell exactly what this tool mutates 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 Guidelines4/5

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

Provides explicit trigger phrases ('attach my Custom Schema {id} to scraper {id}', 'switch scraper {id} to schema {id}') that define when the tool applies. It stops short of naming an alternative for adjacent operations, so there is no when-not guidance, but the positive contexts are concrete.

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.