Skip to main content
Glama

scrapewise_update_scraper_group_schedule

Idempotent
        Sets the group's run schedule and makes the group GOVERN every scraper in it — the group
        schedule overrides each scraper's own. Plan-feature gated per frequency. startType=NONE
        turns governance off ("each scraper decides"): scrapers then run on their own schedules.

        Args:
          - id (string, path param, required): the group's MongoDB ObjectId.
          - body (GroupScheduleDTO, required): startType (NONE | DAILY | EVERY_N_DAYS | WEEKLY |
            MONTHLY) plus scheduleDetails — intervalDays (EVERY_N_DAYS, 1..366), daysOfWeek
            (WEEKLY, non-empty), monthlyDay (MONTHLY, FIRST | LAST).

        Returns:
          The updated GroupDTO (startType, scheduleDetails, groupGovernsSchedule).

        Examples:
          - Use when: "run group {id} every Monday and Thursday" → startType=WEEKLY,
            scheduleDetails.daysOfWeek=[MONDAY,THURSDAY]
          - Use when: "run group {id} on the last day of each month" → startType=MONTHLY,
            scheduleDetails.monthlyDay=LAST
          - Use when: "let each scraper in group {id} keep its own schedule" → startType=NONE
          - Don't use when: you only need a coarse start type without details → use
            scrapewise_update_scraper_group_start_type

        Error Handling:
          - 400 if the schedule details don't match the start type (e.g. WEEKLY without days).
          - 402 if the customer plan lacks the chosen frequency's scheduler feature.
          - 400 (CustomerError) 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>",
      "body": "<body>"
    },
    "name": "scrapewise_update_scraper_group_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe group's MongoDB ObjectId.
bodyYesstartType (NONE | DAILY | EVERY_N_DAYS | WEEKLY | MONTHLY) plus scheduleDetails — intervalDays (EVERY_N_DAYS, 1..366), daysOfWeek (WEEKLY, non-empty), monthlyDay (MONTHLY, FIRST | LAST).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / body / description
      Added value: +"startType (NONE | DAILY | EVERY_N_DAYS | WEEKLY | MONTHLY) plus scheduleDetails — intervalDays (EVERY_N_DAYS, 1..366), daysOfWeek (WEEKLY, non-empty), monthlyDay (MONTHLY, FIRST | LAST)."
    • addedInput schema / properties / id / description
      Added value: +"the group's MongoDB ObjectId."
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover only the mutation/safety profile (readOnlyHint=false, idempotent, non-destructive); the description adds the behavior that actually matters: group-level schedule governance overriding per-scraper schedules, startType=NONE disabling governance, plan-feature gating per frequency, and full HTTP error semantics (400/402/401/500). The 402 plan-gating disclosure in particular is not obtainable from any structured field.

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 purpose sentence, then Args/Returns/Examples/Error Handling in scannable blocks; every section carries real information. Slight redundancy in the Args block, which duplicates the schema's own parameter description verbatim.

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 2-parameter mutation with no output schema, the definition supplies the call semantics, the return shape (GroupDTO with startType, scheduleDetails, groupGovernsSchedule), validation rules, plan-gating failure mode, and worked examples. Nothing an agent needs to invoke it correctly is missing; the runtime hint about dynamic JSON responses is also accounted for by naming the key fields rather than a fixed shape.

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 would be 3, but the description adds semantics the schema lacks: what startType=NONE *means* (governance off, each scraper decides) and worked mappings from natural-language requests to concrete enum payloads. Minor deduction because the Args section largely restates the schema and lists the startType enum as 'NONE | DAILY | EVERY_N_DAYS | WEEKLY | MONTHLY' while the schema also permits MANUAL — an omission that could mislead an agent away from a valid value.

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 ('Sets the group's run schedule') plus the crucial side effect ('makes the group GOVERN every scraper in it — the group schedule overrides each scraper's own'). That override semantics alone distinguishes it from sibling schedule tools.

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 three concrete 'Use when' phrasings mapped to concrete payloads and an explicit 'Don't use when' routing to scrapewise_update_scraper_group_start_type for coarse start types without details. No inference required to pick between them.

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.