Skip to main content
Glama
bruhsb
by bruhsb

paperclip_update_routine_trigger

DestructiveIdempotent

Update the kind or cron schedule of an existing routine trigger to adjust its execution frequency or event type.

Instructions

Update an existing routine trigger's kind or cron schedule.

Args:

  • triggerId: string — Routine trigger UUID (example: "trg_abc123")

  • kind: string (optional) — New trigger kind: schedule | webhook | api

  • cronExpression: string (optional) — New 5-field cron expression (example: "0 9 * * 1-5")

  • timezone: string (optional) — New timezone for schedule triggers

Returns: Returns the updated trigger object: id, routineId, kind, cronExpression, updatedAt.

Examples:

  • Use when: changing a routine from every 5 minutes to daily at 9 AM on weekdays

  • Don't use when: you need to add a new trigger — use paperclip_add_routine_trigger instead

Error Handling:

  • 400: invalid cron expression → ensure 5 whitespace-separated fields

  • 401: authentication failed → check PAPERCLIP_API_KEY

  • 404: trigger not found → verify ID with paperclip_get_routine

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
triggerIdYesRoutine trigger UUID
kindNoNew trigger kind
cronExpressionNoNew 5-field cron expression for schedule triggers
timezoneNoNew timezone for schedule triggers
Behavior4/5

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

Annotations already indicate destructive and idempotent behavior. Description adds return object details and common error codes, but could further clarify consequences of updating a schedule on ongoing tasks.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with clear sections (purpose, args, returns, examples, error handling). Front-loaded and no unnecessary words.

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?

Given 4 parameters, no output schema, and annotations, the description adequately covers purpose, usage context, return object, and error handling. It explains optional parameters and gives concrete examples.

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?

Input schema has 100% description coverage, so description adds limited new semantic value. It provides examples for triggerId and cronExpression, but these are minor additions.

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?

Description clearly identifies the verb 'Update' and resource 'routine trigger', specifying what can be changed (kind or cron schedule). Differentiates from siblings by providing an explicit alternative for adding triggers.

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 concrete examples of when to use (changing a schedule) and explicitly advises against using for adding new triggers, pointing to the sibling tool paperclip_add_routine_trigger. Error handling further guides correct usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bruhsb/paperclip-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server