Skip to main content
Glama

scrapewise_update_scraper_group_ai_control

Idempotent
        Turns "AI control" on or off for one group. When on, on the chosen schedule, the AI
        reviews the latest run of every scraper in the group, detects broken or degraded
        results, proposes a fix, checks the fixed results on real pages before using them,
        and undoes a fix when the next real run is worse. It can repair scrapers that read the
        page with selectors (built automatically or by hand), and JSON-LD and API scrapers; we
        switch each kind of repair on. AI-schema scrapers are checked and you get an alert;
        they are not repaired yet. Supplier endpoints and uploaded files are not checked.
        There are no other customer settings.

        During the test phase some problems are only recorded, not repaired. Use
        scrapewise_get_scraper_group_ai_control_status to see the next check and the last
        result.

        Switching on is available after the account's first wallet top-up (or a paid plan).
        Switching off is always allowed. Changing the frequency or switching off and on again
        never brings the next review earlier than the chosen frequency allows.
        When switched on, a first check is queued right away if the group is due; it usually
        starts within minutes.

        Args:
          - id (string, path param, required): the group's MongoDB ObjectId.
          - body (GroupAiControlDTO, required): enabled — true/false; cadence — DAILY,
            TWICE_WEEKLY or WEEKLY (optional; omitted keeps the current choice, default WEEKLY).

        Returns:
          The updated GroupDTO, carrying aiControlEnabled and aiControlCadence.

        Examples:
          - Use when: "let AI check and fix the scrapers in group {id} every week" →
            enabled=true, cadence=WEEKLY
          - Use when: "check group {id} every day" → enabled=true, cadence=DAILY
          - Use when: "stop the AI from changing scrapers in group {id}" → enabled=false
          - Don't use when: you want to change one scraper's selectors yourself → edit the
            scraper (scrapewise_create_scraper with its id — it creates or updates).

        Error Handling:
          - 402 (PlanError) when switching on before the account's first wallet top-up.
          - 400 (CustomerError envelope) if no group with the given id exists for this
            customer, or the cadence is not one of the three values.
          - 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_group_ai_control"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe group's MongoDB ObjectId.
bodyYesSwitch group AI control on or off and choose how often it runs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / id / description
      Added value: +"the group's MongoDB ObjectId."
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false), the description discloses what the AI actually does (detect, propose, verify on real pages, roll back), which scraper kinds are repaired versus only alerted, that supplier endpoints and uploaded files are excluded, and the wallet-top-up prerequisite for enabling. It also states scheduling behavior (frequency changes never bring the next review forward) and a queued first check. The only minor gap is that the idempotency claim in annotations isn't discussed in prose.

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: purpose first, then behavior, then Args/Returns/Examples/Errors in labeled sections. The behavior paragraph is dense but each clause (which scraper types, what is excluded) earns its place; a few sentences, such as 'There are no other customer settings,' are 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 two-parameter mutation tool with no output schema, the description covers return shape (updated GroupDTO with aiControlEnabled and aiControlCadence), prerequisites, status-code error handling including the 402 PlanError case, and where to look for results afterwards. An agent has everything needed to call it and interpret failures.

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% and the schema already documents both the ObjectId and the cadence enum with its default. The Args section largely restates that, adding only the nuance that omitting cadence keeps the current choice, which is already in the schema description, so it does little work beyond 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?

The opening sentence names a specific verb+resource+scope: turning AI control on or off for one scraper group, with a cadence choice. It also implicitly distinguishes itself from the status getter by pointing to scrapewise_get_scraper_group_ai_control_status for reading state.

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?

A dedicated 'Use when' block gives four concrete phrasings mapped to parameter values, plus an explicit 'Don't use when' that routes the agent to editing a single scraper instead. Both inclusion and exclusion guidance are present.

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.