Skip to main content
Glama

Duplicate a post

clipember_duplicate_post

Copy a post group (every network/account of one video — groupId from clipember_list_scheduled_posts or clipember_create_post) as a new DRAFT: same video, accounts, captions, network settings (YouTube title, LinkedIn visibility, …) and tags. It is not scheduled: the user picks a time and schedules it in the editor (https://clipember.com/schedule//edit), or — once the user tells you the time — you queue each post with clipember_update_post {status: "queued", scheduledFor}. NOT copied: the TikTok choice (who can see it, interactions, disclosure) — each TikTok post of the copy waits for a new choice made for that post (clipember_set_tiktok_choice, only with the user's explicit answer); the client approval and preview link; the repeat. Works for any post, including published or failed ones.

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": {
      "groupId": "<groupId>"
    },
    "name": "clipember_duplicate_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupIdYesThe groupId of the post to copy

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only tell us this is a non-read-only, non-destructive, non-idempotent write; the description adds the substantive behavior the agent actually needs — the result is an unscheduled DRAFT, exactly which fields carry over (video, accounts, captions, YouTube title, LinkedIn visibility, tags), and what is deliberately dropped (TikTok visibility choice, client approval, preview link, repeat). The TikTok caveat is especially valuable because it forces a follow-up user interaction before the copy is postable.

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?

Front-loaded with the outcome (new DRAFT copy) before the caveats, and each clause carries operational content rather than restating the name. It is dense and parenthesis-heavy, verging on a run-on sentence in the middle, but no sentence is filler.

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?

For a one-parameter, non-destructive mutation with no output schema, the definition covers outcome, copied vs. omitted fields, the non-scheduled state, and the exact follow-up tools and preconditions. Nothing an agent needs in order to call this correctly, or to explain the result to a user, is missing.

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 100% and the single groupId is already documented, so the schema does the heavy lifting. The description nonetheless adds provenance the schema lacks — groupId comes from clipember_list_scheduled_posts or clipember_create_post — which tells the agent where to source the value rather than how to format it.

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?

States a precise verb and resource: 'Copy a post group ... as a new DRAFT', and immediately scopes it ('every network/account of one video') with a concrete definition of groupId. The draft-vs-scheduled distinction separates it cleanly from clipember_create_scheduled_post and clipember_update_post without requiring the agent to open 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 explicit routing: use the editor link if the user picks the time, use clipember_update_post {status: "queued", scheduledFor} once the time is known, and use clipember_set_tiktok_choice only with an explicit user answer. It also states the validity envelope ('works for any post, including published or failed ones'), so neither the when-to-use nor the when-not is left to inference.

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