Skip to main content
Glama

scrapewise_create_scraper_group

        Create-or-update by id semantics: empty `id` in the body creates a new group;
        non-empty `id` updates the existing group with that id. Creating is
        plan-feature gated by MAX_GROUPS limit; updating is not gated.

        Args:
          - body (GroupDTO, required): full group definition. Set `id` to update;
            omit to create. Includes name, dataTable name, schedule, etc.

        Returns:
          The persisted GroupDTO including the (possibly newly assigned) id and
          server-stamped fields.

        Examples:
          - Use when: "create a new group called 'türklased'" → body with id omitted
          - Use when: "rename group {id} to 'X'" → body with id set + new name
          - Don't use when: you want to delete → use scrapewise_delete_scraper_group

        Error Handling:
          - 402 if customer plan's MAX_GROUPS limit is reached on a create.
          - 400 if body validation fails.
          - 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": {
      "body": "<body>"
    },
    "name": "scrapewise_create_scraper_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesfull group definition. Set `id` to update; omit to create. Includes name, dataTable name, schedule, etc.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / body / description
      Added value: +"full group definition. Set `id` to update; omit to create. Includes name, dataTable name, schedule, etc."
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations it discloses the plan-feature gating asymmetry (creates are gated by MAX_GROUPS, updates are not), that the response is the persisted DTO with server-stamped fields, and a full error map (402 on group-limit, 400 validation, 401, 500). These are non-obvious behaviors an agent cannot infer from readOnlyHint/destructiveHint alone.

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?

Content is front-loaded with the decisive create/update rule before Args/Returns/Examples/Error Handling, and each block is scannable. Minor waste: the Args block largely restates what the 100%-covered schema already documents, so a sentence or two could be trimmed without loss.

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 mutation tool with a large nested body, no output schema, and no reliance on structured annotations for error semantics, the description covers entry conditions, return shape, failure modes, and the create/update fork. Nothing an agent needs in order 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.

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns an extra point by explaining the create-vs-update meaning of the `id` field, characterizing `body` as a "full group definition" (not a partial patch), and noting that `confirmedAt` inside priceMonitor is server-stamped and ignored on write — meaning that is absent from the schema.

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 very first line states the exact behavior: "Create-or-update by id semantics: empty `id` in the body creates a new group; non-empty `id` updates the existing group with that id." This resolves the ambiguity created by the tool name (which only says "create") and pins down a specific verb pair plus the discriminating condition.

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?

It gives concrete when-to-use examples ("create a new group called 'türklased'", "rename group {id} to 'X'") and an explicit when-not-to-use with the named alternative: "Don't use when: you want to delete → use scrapewise_delete_scraper_group". That is the full when/when-not/alternative triad.

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.