Skip to main content
Glama
bruhsb
by bruhsb

paperclip_add_routine_trigger

Add a schedule, webhook, or API trigger to your routine. Define a cron expression for scheduled triggers to automate recurring execution.

Instructions

Add a trigger to a routine. Supports schedule (cron), webhook, and api trigger kinds.

Args:

  • routineId: string — Routine UUID (example: "rtn_abc123")

  • kind: string — Trigger kind: schedule | webhook | api

  • cronExpression: string (optional) — 5-field cron expression, required for schedule triggers (example: "*/5 * * * *")

  • timezone: string (optional) — Timezone for schedule triggers (default: UTC)

Returns: Returns the created trigger object: id, routineId, kind, cronExpression, createdAt.

Examples:

  • Use when: scheduling a routine to run every 5 minutes after creating it

  • Don't use when: the trigger already exists — use paperclip_update_routine_trigger to modify it

Error Handling:

  • 400: invalid cron expression → must be a 5-field cron (e.g. '*/5 * * * *')

  • 401: authentication failed → check PAPERCLIP_API_KEY

  • 404: routine not found → verify ID with paperclip_list_routines

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
routineIdYesRoutine UUID
kindYesTrigger kind: schedule | webhook | api
cronExpressionNo5-field cron expression for schedule triggers (e.g. '*/5 * * * *'). Required when kind is 'schedule'.
timezoneNoTimezone for schedule triggers (e.g. 'UTC', 'America/New_York'). Default: UTC
Behavior4/5

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

While annotations are minimal (destructiveHint: false), the description adds behavioral context: creation action, error codes (400, 401, 404), and implication that duplicate triggers are not allowed. Lacks details on idempotency or rate limits, but adequate for a creation tool.

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?

Well-structured with summary, args, returns, examples, and error handling sections. Front-loaded with purpose. Some minor redundancy (e.g., param descriptions overlap schema) but overall efficient.

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 no nested objects, the description fully specifies inputs, returns (fields), error cases, and usage context. No critical 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 covers all 4 parameters (100%), but description adds value with examples (e.g., routineId), enum meaning, cron format clarification, timezone default, and error conditions. Exceeds baseline 3.

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?

Explicitly states 'Add a trigger to a routine' with specific verb and resource, and distinguishes from siblings like paperclip_update_routine_trigger and paperclip_delete_routine_trigger through usage guidance and error handling.

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 explicit when-to-use and when-not-to-use guidance, including a direct sibling alternative ('use paperclip_update_routine_trigger'). Also implies verification with paperclip_list_routines for 404 errors.

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