Skip to main content
Glama

tailor_draft

Rewrite an existing post for ANOTHER platform, with AI. Runs the voice engine. Use for "rewrite 123 for Twitter", "make that work on LinkedIn". Pass save_as: "channel_copy" to save the rewrite on the same post as that channel's own copy (it keeps its media and schedule, and that text publishes on that channel). Do that when the user wants one post on several channels with different text. The default, "new_draft", saves it as a separate draft. Either way the reply shows the rewritten text and the id of the post it is on. Not for feedback like "shorter" (that is revise_draft), not for text you wrote (that is update_draft with channel_copies), and not for several versions to pick from (that is draft_variations).

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": {
      "id": "<id>",
      "platform": "<platform>"
    },
    "name": "tailor_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPost id to rewrite
save_asNo"channel_copy": write the rewrite onto this post as the platform's own copy. "new_draft" (default): save it as a separate draft.
platformYesTarget platform. For Instagram, only `save_as: "channel_copy"` on a post that already has an image or video.
workspaceNoOptional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / workspace
      Added value: +{
      +  "description": "Optional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false). The description adds genuine behavioral context beyond them: what each save mode creates, that media and schedule are preserved on channel_copy, that the mutated text publishes on that channel, and what the reply contains.

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?

Purpose is front-loaded and every sentence carries a rule, an example, or an exclusion rather than filler. It is dense — the save_as explanation, the reply contents, and three sibling exclusions run together in a long block — costing a point on readability, but not on substance.

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?

There is no output schema, and the description compensates by stating that the reply returns the rewritten text and the post id. Combined with the channel_copy media/schedule persistence and the default mode, an agent has everything needed to call this correctly and report results.

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 coverage is already 100%, so the schema carries the definitions, yet the description adds the decision rule for `save_as` (channel_copy when the user wants one post on several channels; new_draft as the default) that the schema only states mechanically. Platform and workspace semantics are left to the schema, which is acceptable at full coverage.

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?

The first sentence names a specific verb and resource ("Rewrite an existing post for ANOTHER platform") and the closing sentence explicitly distinguishes it from three siblings: revise_draft, update_draft, and draft_variations. An agent can select this tool without opening any schema.

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?

Gives concrete user phrasings ("rewrite 123 for Twitter", "make that work on LinkedIn") plus an explicit when-to-use condition for `save_as: "channel_copy"` (one post across several channels with different text). It also names three exclusions with the alternative to use instead, which is the full when/when-not/alternatives set.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources