Skip to main content
Glama

scrapewise_create_scraper_v2

        Same create-or-update semantics as `scrapewise_create_scraper` (empty `id` →
        insert; non-empty `id` → update by id with ownership check), but the response
        is the richer `ScraperSuperDTO` shape: configValid flag, full schema body
        inline, full group body inline, computed last-N-run stats. Use V2 when the
        agent needs to confirm the resulting state in one round-trip without a
        follow-up `scrapewise_get_scraper_v2` call. V2 is the preferred shape for new
        tooling.

        Args:
          - body (ScraperDTO, required): same shape as scrapewise_create_scraper —
            full configuration including name, type, sourceConfig, itemsConfig,
            pagination, optional schema reference, postProcessRules, group association.

        Returns:
          ScraperSuperDTO — a strict superset of ScraperDTO so V1 consumers can ignore
          the extra fields. The newly minted id (on insert) lands in the response;
          capture it for follow-up calls.

        Examples:
          - Use when: agent needs the full enriched state immediately after writing
          - Use when: building a wizard-style UI that needs schema + group inline
          - Don't use when: agent only needs the bare ScraperDTO (use V1 to save bytes)
          - Don't use when: you have many URLs to scrape. Do NOT create one scraper per URL.
            Create ONE scraper and attach the addresses as its link list —
            `scrapewise_run_scraper_url_list` does the whole thing in one call, or
            `scrapewise_create_scraper_site` attaches a list to a scraper you already have.

        Error Handling:
          Same as scrapewise_create_scraper (400 validation; 400 CustomerError on
          cross-tenant id forge; 402 on plan limit; 401 / 500 standard).

[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_create_scraper_v2"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYessame shape as scrapewise_create_scraper — full configuration including name, type, sourceConfig, itemsConfig, pagination, optional schema reference, postProcessRules, group association.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / body / description
      Added value: +"same shape as scrapewise_create_scraper — full configuration including name, type, sourceConfig, itemsConfig, pagination, optional schema reference, postProcessRules, group association."
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare it as a non-read-only, non-destructive, non-idempotent write; the description goes well beyond that with ownership checks on id forge, enumerated error codes (400/402/401/500), and the id-in-response capture requirement. The one gap is that it never says whether an update replaces the entire configuration or merges with existing fields, which matters for a create-or-update mutation.

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 structured with Args/Returns/Examples/Error Handling sections and the key V1-vs-V2 distinction front-loaded. Some redundancy between the Returns paragraph and the examples, but no sentence is wasted for a mutation tool of this complexity.

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?

There is no output schema, so the description carries the return contract and does so fully (ScraperSuperDTO, superset of ScraperDTO, newly minted id). The runtime hint additionally warns that the actual response is a dynamic string-or-object blob, so nothing an agent needs to call and parse this 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?

Schema coverage is 100%, so the nested body is already documented; the description mainly recaps top-level fields (name, type, sourceConfig, itemsConfig, pagination, postProcessRules, group). It does add one genuinely undocumented semantic — empty `id` means insert, non-empty `id` means update by id — which the schema's bare `id` field does not state, keeping this at baseline-plus rather than 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 first sentence states the specific verb pair and resource (create-or-update a scraper) and immediately differentiates V2 from `scrapewise_create_scraper` by its richer `ScraperSuperDTO` response. An agent can distinguish this from the V1 sibling without opening either 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?

Explicit 'Use when' / 'Don't use when' blocks name alternatives and the conditions that select them: V1 for the bare DTO, `scrapewise_run_scraper_url_list` or `scrapewise_create_scraper_site` when many URLs must be attached. It even pre-empts a common misuse ('Do NOT create one scraper per URL').

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.