duplicate-automationCopy an automation with its trigger, conditions, webhook and documents. The copy is named after the original with "(Copy)" appended and starts out active.
| Name | Required | Description | Default |
|---|---|---|---|
| automation_id | Yes | The id of the automation to copy. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotation already indicates non-destructive. Description adds naming convention ('(Copy)' appended) and initial active state. However, lacks details on permissions required or behavior if original is deleted.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences with no redundancy. Front-loaded with action. Every sentence adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simple tool with one parameter and high schema coverage, the description covers the key behavior. However, no mention of return value or error scenarios, though not required since no output schema. Adequate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% for the single parameter, and the description does not add additional semantics beyond the schema. Baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states 'Copy an automation' with specific details on what is included (trigger, conditions, webhook, documents). Distinguishes from sibling tools like create-automation or activate-automation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Description implies usage for duplicating an automation but does not explicitly state when to use this tool vs alternatives like create-automation or deactivate-automation. No when-not conditions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct operation (document management, PDF manipulation, automation, analytics, etc.) with clear boundaries, making it easy for an agent to select the correct one.
All tool names follow a strict lowercase-with-hyphens pattern and use consistent verb-noun phrasing (e.g., 'create-document', 'list-documents', 'add-pdf-security'), ensuring predictability.
At 45 tools, the server far exceeds the recommended 3-15 range for a well-scoped set. While the coverage is comprehensive, the high number may overwhelm agents and suggests insufficient consolidation.
The tool surface covers the full lifecycle of documents and PDFs—creation, retrieval, update, deletion, archiving, security, OCR, splitting, merging, automation, analytics, and more—with no obvious gaps.