Skip to main content
Glama

scrapewise_update_matcher_schedule

DestructiveIdempotent
        Sets the schedule of the group's current matching setup, or clears it with a null body. It does NOT
        start a run and does not change the setup or its results (a PUT of the setup would replace the results
        and run). A new or changed schedule starts from now: missed earlier times are not run.

        Args:
          - id (string, path, required): the group's id.
          - idempotency_key (string, query): REQUIRED for AI-agent keys. A new value for each new change; the
            same value only to retry that same change.
          - body (MatcherScheduleDTO or null): type AFTER_SCRAPES (re-run after each scrape), DAILY, EVERY_N_DAYS
            (intervalDays 1..366) or WEEKLY (daysOfWeek, at least one, e.g. ["MONDAY"]); calendar types need
            time ("HH:mm", 24 h) and take zone (IANA id, default Europe/Tallinn). null = run once (clears it).
            scheduledAutoMatches (optional): KEEP_ADD (default; delivered matches stay, new ones are added) or
            REPLACE (each scheduled run replaces the matches). Scheduled runs always keep review decisions.
          - customerRef (string, query, optional): only for a Scrapewise admin key while the admin works in
            another customer's account (Take Over): the customerUniqueRef of that customer. Required then
            (409 TAKE_OVER_ACTIVE without it); leave it out otherwise.

        Returns:
          The MatcherJobDTO with schedule, lastScheduledRun, scheduleDueAt, nextRunAt and the new version.

        Examples:
          - Use when: "match group {id} every Monday at 06:00 Tallinn time" -> {"type":"WEEKLY",
            "daysOfWeek":["MONDAY"],"time":"06:00","zone":"Europe/Tallinn"}.
          - Use when: "stop the automatic matching of group {id}" -> body null.
          - Don't use when: you want to change the setup itself -> scrapewise_update_matcher_job.

        Error Handling:
          - 400 IDEMPOTENCY_KEY_REQUIRED: an AI-agent key sent no idempotency_key. Nothing was changed.
          - 400 (CustomerError): a bad schedule field (the message names it); 400 FIELD_INVALID: a bad
            scheduledAutoMatches value.
          - 404: the group has no matching setup yet, an unknown group, or another customer's group.
          - 409: the setup was replaced by a save meanwhile — read it again and retry with a new key.
          - 409 IDEMPOTENCY_IN_FLIGHT (an idempotency conflict): retry after a second.
          - 409 TAKE_OVER_ACTIVE: this key's admin works in another customer's account — end Take Over or
            send customerRef=<that customer's ref>.
          - 429 OWNER_EDIT_RATE_LIMIT (owner of a group on the newer engine): more than 10 changes of this group
            in 10 minutes; wait Retry-After seconds, then retry (the SAME idempotency_key may be reused).
          - 401 Unauthorized; 403 for a read-only key or a plan without matching.
          - 5xx: read the setup again (scrapewise_get_matcher_job) before retrying.
          Nothing was changed in each. The answer's version is new: a save built from an earlier read is 409
          VERSION_CHANGED (read again first).

[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>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "scrapewise_update_matcher_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe group's id.
bodyNotype AFTER_SCRAPES (re-run after each scrape), DAILY, EVERY_N_DAYS (intervalDays 1..366) or WEEKLY (daysOfWeek, at least one, e.g. ["MONDAY"]); calendar types need time ("HH:mm", 24 h) and take zone (IANA id, default Europe/Tallinn). null = run once (clears it).
customerRefNoAdmin keys in Take Over only: the customerUniqueRef of the customer the admin works for. Required then; leave it out otherwise.
idempotency_keyYesRequired for AI-agent keys: a new value per new change, the same value only to retry it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / body / description
      Added value: +"type AFTER_SCRAPES (re-run after each scrape), DAILY, EVERY_N_DAYS (intervalDays 1..366) or WEEKLY (daysOfWeek, at least one, e.g. [\"MONDAY\"]); calendar types need time (\"HH:mm\", 24 h) and take zone (IANA id, default Europe/Tallinn). null = run once (clears it)."
    • addedInput schema / properties / id / description
      Added value: +"the group's id."
  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, the description explains that the tool does not start a run or change setup/results, that new or changed schedules start from now with missed times not run, that scheduled runs keep review decisions, and how scheduledAutoMatches behaves. It also documents idempotency key requirements, Take Over semantics, rate limit behavior, and many error modes, which is substantially richer than the annotations 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?

The description is long but well structured and front-loaded with purpose, exclusions, arguments, returns, examples, and error handling. Some schedule field details repeat the schema body description and the error list is verbose, but the sections are organized and mostly earn their place.

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?

This is a complex mutation with a nested body and no output schema, yet the description covers return fields, schedule semantics, idempotency, Take Over behavior, rate limits, and detailed error handling. Nothing critical for correct invocation appears 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 description coverage is already 100%, so the schema carries most parameter semantics. The description still adds useful operational meaning: the idempotency key must be new per change and reused only for retry, customerRef is required only during an admin Take Over, and null body means run once and clears the schedule.

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 description states a specific verb and resource: it sets or clears the schedule for a group's current matching setup. It explicitly distinguishes the tool from starting a run and from changing the setup/results, and names scrapewise_update_matcher_job as the alternative for setup changes.

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 provides explicit 'Use when' examples, including a concrete Monday schedule and stopping automatic matching with a null body. It also contains an explicit 'Don't use when' route to scrapewise_update_matcher_job for setup changes, leaving little inference for the agent.

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.