Skip to main content
Glama

create_recurring_task

Create recurring task schedules that automatically spawn instances on daily, weekly, or custom cadences, with each instance receiving the previous summary for automated reports, checks, and audits.

Instructions

Creates a recurring task schedule that automatically spawns task instances on a schedule. Each instance gets access to the previous instance's summary. Suited to regular automated work such as weekly reports, daily checks and periodic audits.

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": {
      "project_id": "<project_id>",
      "title_template": "<title_template>",
      "frequency": "<frequency>"
    },
    "name": "create_recurring_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelsNoLabels to apply to each instance.
ends_atNoWhen to stop the schedule (RFC3339). Default: no end.
priorityNoPriority: urgent, high, medium, low, none.none
timezoneNoIANA timezone for schedule evaluation. Default: UTC.
cron_exprNo5-field cron expression (required if frequency=custom). Example: '0 9 * * 1' = every Monday at 9am.
frequencyYesRecurrence frequency: daily, weekly, monthly, custom. Use 'custom' with cron_expr for fine-grained control.
starts_atNoWhen to start the schedule (RFC3339). Default: now.
project_idYesTarget project UUID.
assignee_idNoAgent or user UUID to assign each instance.
assignee_typeNoAssignee type: user, agent, unassigned.unassigned
max_instancesNoMaximum number of instances to create. Default: unlimited.
title_templateYesTask title template. Supports {{.Date}}, {{.Number}}, {{.Week}}, {{.Month}}.
description_templateNoTask description template. Also supports {{.PrevSummary}} for previous instance context.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations cover the safety profile (not read-only, not destructive, not idempotent), and the description adds substantive behavior beyond them: instances are auto-spawned and each gets the previous instance's summary. It doesn't explain permissions or what happens on schedule end/update, but the core mechanism is disclosed.

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?

Three tight sentences with the core action front-loaded. Minor redundancy in repeating 'on a schedule,' but nothing wasteful.

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

Completeness3/5

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

For a 13-parameter mutation tool with no output schema, the description covers purpose and the instance-chaining behavior but says nothing about what is returned or the schedule's lifecycle (e.g., ends_at, max_instances interplay). The rich schema fills most gaps, leaving this adequate but not complete.

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%, so the schema already documents all 13 parameters, including the templating placeholders and cron usage. The description adds little parameter-level meaning beyond mentioning that instances receive the prior summary, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: creates a recurring task schedule that spawns task instances. It's clearly distinct in meaning from create_task (one-off) and trigger_recurring_now, though it never names those siblings explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides concrete usage contexts ('weekly reports, daily checks and periodic audits'), which tells an agent when this is the right choice. It stops short of exclusions or naming alternatives like create_task for one-off work, so it's clear context without routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.