Skip to main content
Glama

scrapewise_run_scraper_group

        Triggers a manual run of EVERY scraper that belongs to the given group. Each
        scraper's run is queued asynchronously (same semantics as scrapewise_run_scraper
        for an individual scraper). Optional `mergeData=true` combines the per-scraper
        results into a single enriched dataset on completion. Requires the
        RUN_WITH_GROUP plan feature.

        Args:
          - id (string, path param, required): the group's MongoDB ObjectId.
          - mergeData (boolean, query param, optional, default false): if true, after
            all per-scraper runs complete, the data is merged into the group's enriched
            sibling collection.

        Returns:
          200 OK with `{"firstJob": boolean}` — true only when a signed-in user starts their very
          first run by hand; always false for API keys. Poll scrapewise_get_scraper_load_history per scraper, or
          read scrapewise_get_scraper_group_list to see lastRunState across the group.

        Examples:
          - Use when: "run all scrapers in group {id}" → id only
          - Use when: "run group {id} and merge results" → mergeData=true
          - Don't use when: you want to run just one scraper → use scrapewise_run_scraper

        Error Handling:
          - 402 if customer plan lacks RUN_WITH_GROUP feature.
          - 402 WALLET_INSUFFICIENT_BALANCE, raised SYNCHRONOUSLY before anything is queued, when
            the pay-as-you-go wallet is on and the customer has neither balance nor free requests.
            Nothing runs and nothing is charged; top up and retry.
          - 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>"
    },
    "name": "scrapewise_run_scraper_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe group's MongoDB ObjectId.
mergeDataNoif true, after all per-scraper runs complete, the data is merged into the group's enriched sibling collection.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / id / description
      Added value: +"the group's MongoDB ObjectId."
    • addedInput schema / properties / mergeData / description
      Added value: +"if true, after all per-scraper runs complete, the data is merged into the group's enriched sibling collection."
  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: explains that each run is queued asynchronously (mirroring scrapewise_run_scraper), that mergeData produces a merged enriched sibling collection on completion, that RUN_WITH_GROUP plan gating applies, and that the wallet error is raised synchronously before anything is queued so nothing runs or is charged. Documents the 402/400/401/500 error envelopes and how to poll for status, which is exactly the context annotations cannot convey.

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-loads the core behavior in the first sentence and then uses cleanly labeled Args/Returns/Examples/Error Handling sections, so an agent can skim to what it needs. The Args section is somewhat redundant with the schema, which is the only real waste.

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 an async, plan-gated mutation with no output schema, the definition supplies the return shape ({firstJob: boolean}), the polling alternatives (load history per scraper, group list for lastRunState), plan prerequisites, and full error semantics. The runtime hint also warns the response is a dynamic blob to parse defensively, closing the outputSchema gap.

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 description coverage is 100% and the schema's own descriptions nearly duplicate the Args section text for id and mergeData. The description adds only marginal framing (path param vs query param, default false) and confirms merge happens only after all per-scraper runs complete — useful but largely restated from structured data.

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 with explicit scope: 'Triggers a manual run of EVERY scraper that belongs to the given group', and immediately contrasts it with running one scraper via scrapewise_run_scraper. The agent can distinguish this from the single-scraper sibling without reading 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?

Provides concrete invocation examples ('run all scrapers in group {id}' → id only; 'run group {id} and merge results' → mergeData=true) plus an explicit 'Don't use when' clause routing to scrapewise_run_scraper. When-to-use and when-not-to-use are both covered.

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.