Clone an existing post into a new draft while preserving content, connected accounts, and per-account overrides. Use it to reuse or adapt scheduled posts without starting from scratch.
Clone an existing post as a new draft. Copies content, accounts, and per-account overrides.
| Name | Required | Description | Default |
|---|---|---|---|
| post_id | Yes | Post ID to duplicate. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, the description carries full burden. It only mentions what is copied but omits crucial behavioral details such as whether the original post remains unchanged, what the result is (e.g., new post ID), any permissions needed, or error conditions. This is insufficient for a mutation tool.
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?
The description is a single sentence with no wasted words. It is front-loaded with the core action and follows with what is copied. Very concise.
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?
The description covers the core functionality but omits important context such as what the tool returns (e.g., new post draft ID), whether the original post is modified, and any required permissions. Given the low complexity, it is just barely adequate but leaves gaps.
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?
Since schema coverage is 100%, the description does not add parameter semantics beyond the schema definition. The parameter description in the schema is already clear. Baseline score of 3.
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?
The description uses the specific verb 'Clone' and clarifies the destination (new draft). It also lists the copied attributes, providing clear differentiation from sibling tools like create_post or update_post.
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?
The description provides no explicit guidance on when to use this tool versus siblings like create_post or update_post. It merely states what it does, leaving the agent to infer usage from the tool name and sibling list.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.