Skip to main content
Glama

Update repeating task

update_repeating_task

Change a repeating series from fromDayKey on ("this and all following"; default: today, or the day of the occurrence id you pass). Earlier days keep the old values. Can change title, time, reminder, daily/weekly, weekday and end day. Weekly series continue on the first matching weekday on or after fromDayKey. The series gets a new id. To change only one day, use update_task on that occurrence instead. Can be reverted with undo_last_change.

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": {
      "templateId": "<templateId>"
    },
    "name": "update_repeating_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
repeatNo
weekdayNoWeekly only: move the series to this day of the week.
endDayKeyNoNew last day (inclusive), or null to repeat forever.
fromDayKeyNoFirst day the change applies to (default: today).
reminderAtNo
templateIdYesRepeating task id (repeatingTaskId / id from list_repeating_tasks, get_week or search_tasks). The id of one of its occurrences also works.
timeMinutesNoNew time, or null for all-day.
reminderMinutesBeforeNoReminder minutes before the time, or null to turn reminders off.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent mutation, so the bar is lower. The description still adds real behavior: earlier days keep old values, weekly series resume on the first matching weekday on or after fromDayKey, and the series receives a new id, which is a consequential side effect an agent would otherwise miss. It stops short of describing permissions or rate limits, keeping it at a 4 rather than a 5.

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 scoping rule is front-loaded and every sentence carries information: fields changeable, weekly resumption rule, new id, alternative tool, undo path. The nested parenthetical in the first sentence makes it slightly run-on, but nothing is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter mutation with no output schema, the description covers the critical behavioral consequences (partial-series semantics, new id, reversibility) and the closest alternative. It omits what the call returns and any precondition on the task being a repeating series, which are minor remaining gaps.

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 67%, so the schema carries most of the parameter detail. The description nonetheless adds semantics the schema does not: the 'this and all following' interpretation of fromDayKey, its default resolution via an occurrence id, and the interaction between weekday and the weekly continuation rule. It does not clarify the reminderAt vs reminderMinutesBefore exclusion beyond what the schema says.

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 ('Change a repeating series') and immediately bounds the scope with 'from fromDayKey on ("this and all following")'. It also names the sibling update_task and the condition that distinguishes it, so an agent can pick between the two without opening 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?

Explicitly routes single-occurrence edits to update_task on that occurrence, and names undo_last_change as the reversal path. The default for fromDayKey (today, or the day of the passed occurrence id) removes the most likely invocation ambiguity.

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.

Resources