Skip to main content
Glama
Hermoso

Hermoso

Official

Duplicate a scheduled post

duplicate_scheduled
Destructive

Copy a scheduled or published post into a new queued post with optional overrides for caption, media, channels, and timing. The copy is independent of the original.

Instructions

Copy an existing scheduled or already-published post into a NEW queued post — the way to run a creative again, reuse a post that worked as the starting point for the next one, or re-send something after it went out. It copies the caption, media, per-channel captions, title, description, tags and the target board / Page / company Page / listing, and ANY of those can be overridden in the same call. Give a new time in at, or useQueue:true to drop it into the brand’s next free posting slot. The copy is INDEPENDENT — editing or cancelling it never touches the original — and it is a genuinely new post rather than a re-send, so it publishes even where the original already did. To re-fire only the channels that FAILED, use retry_scheduled instead.

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>"
    },
    "name": "duplicate_scheduled"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNowhen the copy goes out: local wall clock (2026-10-30T10:00), UTC or epoch ms (default: an hour from now)
idYesthe post to copy, from list_scheduled
linkNodestination URL for the copy (Pinterest, Facebook text post or Google Business post)
brandNoWHICH PROFILE this post is in — id or exact name from list_brands; needed when it is not the profile this connection is pinned to. A name that matches no profile, or two, is REFUSED.
titleNoPinterest or YouTube headline for the copy, max 100 characters
chatIdNoTELEGRAM — which chat, group or channel the copy goes to (@username or numeric id)
ideaIdNoshort id of the content-plan idea this post came from
pageIdNoFACEBOOK / INSTAGRAM / THREADS — which connected Page (list_meta_pages)
recipeNothe post's FORMAT id, e.g. "slideshow" or "imessage_chat" — post_performance groups by it, so reuse one id per format
boardIdNoPINTEREST — the board for the copy (list_pinterest_boards)
messageNoa different caption for the copy
captionsNoper-channel caption overrides for the copy
channelsNopost the copy to these channels instead of the original’s
imageUrlNoreplacement image for the copy: a Hermoso render URL or an upload_file URL
timezoneNoIANA zone for a wall-clock `at` or the queue
useQueueNoinstead of naming a time, take the brand’s next free posting slot
videoUrlNoreplacement video for the copy: a Hermoso render URL or an upload_file URL
imageUrlsNoCAROUSEL — an ORDERED list of image URLs published as ONE swipeable post
locationIdNoGOOGLE BUSINESS — which listing (list_business_locations)
visibilityNopublic (default), unlisted or private (YouTube), or draft (TikTok or an unpublished Facebook Page post)
whopExperienceIdNoWHOP — which forum or chat the copy goes to (exp_…, from list_whop_destinations).
linkedinOrganizationIdNoLINKEDIN — publish the copy as this company Page (list_linkedin_pages)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.571
    • changedInput schema / properties / channels / items / enum
      Previous value: -[
      -  "facebook",
      -  "instagram",
      -  "threads",
      -  "tiktok",
      -  "youtube",
      -  "linkedin",
      -  "x",
      -  "pinterest",
      -  "google_business",
      -  "bluesky",
      -  "telegram",
      -  "wordpress",
      -  "discord",
      -  "slack",
      -  "whop"
      -]New value: +[
      +  "facebook",
      +  "instagram",
      +  "threads",
      +  "tiktok",
      +  "youtube",
      +  "linkedin",
      +  "x",
      +  "pinterest",
      +  "google_business",
      +  "bluesky",
      +  "telegram",
      +  "wordpress",
      +  "discord",
      +  "slack",
      +  "whop",
      +  "shopify_blog",
      +  "webflow",
      +  "wix"
      +]
  2. Changed2 schema fields changedv0.1.519
    • changedInput schema / properties / channels / items / enum
      Previous value: -[
      -  "facebook",
      -  "instagram",
      -  "threads",
      -  "tiktok",
      -  "youtube",
      -  "linkedin",
      -  "x",
      -  "pinterest",
      -  "google_business",
      -  "bluesky",
      -  "telegram"
      -]New value: +[
      +  "facebook",
      +  "instagram",
      +  "threads",
      +  "tiktok",
      +  "youtube",
      +  "linkedin",
      +  "x",
      +  "pinterest",
      +  "google_business",
      +  "bluesky",
      +  "telegram",
      +  "wordpress",
      +  "discord",
      +  "slack",
      +  "whop"
      +]
    • addedInput schema / properties / whopExperienceId
      Added value: +{
      +  "description": "WHOP — which forum or chat the copy goes to (exp_…, from list_whop_destinations).",
      +  "type": "string"
      +}
  3. Changed5 schema fields changedv0.1.465
    • addedInput schema / properties / imageUrl / description
      Added value: +"replacement image for the copy: a Hermoso render URL or an upload_file URL"
    • addedInput schema / properties / link / description
      Added value: +"destination URL for the copy (Pinterest, Facebook text post or Google Business post)"
    • addedInput schema / properties / title / description
      Added value: +"Pinterest or YouTube headline for the copy, max 100 characters"
    • addedInput schema / properties / videoUrl / description
      Added value: +"replacement video for the copy: a Hermoso render URL or an upload_file URL"
    • addedInput schema / properties / visibility / description
      Added value: +"public (default), unlisted or private (YouTube), or draft (TikTok or an unpublished Facebook Page post)"
  4. Changed2 schema fields changedv0.1.454
    • changedInput schema / properties / at / description
      Previous value: -"when the copy goes out — ISO timestamp or epoch milliseconds (default: an hour from now)"New value: +"when the copy goes out: local wall clock (2026-10-30T10:00), UTC or epoch ms (default: an hour from now)"
    • changedInput schema / properties / timezone / description
      Previous value: -"IANA zone for the queue, e.g. \"America/New_York\""New value: +"IANA zone for a wall-clock `at` or the queue"
  5. Changed1 schema field changedv0.1.374
    • changedInput schema / properties / brand / description
      Previous value: -"WHICH BRAND this post is in — id or exact name from list_brands; needed when it is not the brand this connection is pinned to. A name that matches no brand, or two, is REFUSED."New value: +"WHICH PROFILE this post is in — id or exact name from list_brands; needed when it is not the profile this connection is pinned to. A name that matches no profile, or two, is REFUSED."
  6. Changed1 schema field changedv0.1.320
    • changedInput schema / properties / brand / description
      Previous value: -"WHICH BRAND this post is in — the id or exact name from list_brands. Needed when the post lives in a brand this connection is not pinned to: a post you can CREATE in a brand must be manageable there too, without switching the whole connection. A name that matches no brand, or two, is REFUSED."New value: +"WHICH BRAND this post is in — id or exact name from list_brands; needed when it is not the brand this connection is pinned to. A name that matches no brand, or two, is REFUSED."
  7. Changed2 schema fields changedv0.1.281
    • addedInput schema / properties / ideaId
      Added value: +{
      +  "description": "short id of the content-plan idea this post came from",
      +  "type": "string"
      +}
    • addedInput schema / properties / recipe
      Added value: +{
      +  "description": "the post's FORMAT id, e.g. \"slideshow\" or \"imessage_chat\" — post_performance groups by it, so reuse one id per format",
      +  "type": "string"
      +}
  8. Changed1 schema field changedv0.1.251
    • addedInput schema / properties / brand
      Added value: +{
      +  "description": "WHICH BRAND this post is in — the id or exact name from list_brands. Needed when the post lives in a brand this connection is not pinned to: a post you can CREATE in a brand must be manageable there too, without switching the whole connection. A name that matches no brand, or two, is REFUSED.",
      +  "type": "string"
      +}
  9. Addedv0.1.161

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and idempotentHint=false, but the description adds genuinely non-obvious behavior: the copy is independent, editing or cancelling it never touches the original, and it republishes even where the original already ran. It does not explain the auth/permission requirements or why the operation is flagged destructive (a real live publish), which is the remaining gap.

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 core action and the key override/independence properties, and every sentence carries information. It is on the long side, with some restatement between 'genuinely new post rather than a re-send' and the preceding independence clause.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 22-parameter mutation tool with no output schema, the description covers what gets copied, how to override it, how to choose timing, and how the result differs from the original and from retry_scheduled. The missing piece is the permission/credential context that a destructive, non-idempotent publish operation arguably warrants.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description does add override semantics — the caption, media, per-channel captions, title, description, tags and target board/Page/listing are all copied yet 'ANY of those can be overridden in the same call', and `at` vs useQueue selects the timing path. It stops short of adding format or interaction detail beyond that framing.

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 specific verb and resource — copying an existing scheduled or already-published post into a NEW queued post — and explicitly names the sibling it is not (retry_scheduled). An agent can distinguish it from retry_scheduled, reschedule_post, or schedule_post 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 use cases (run a creative again, reuse a post that worked, re-send after it went out) and an explicit exclusion with an alternative: 'To re-fire only the channels that FAILED, use retry_scheduled instead.' It also resolves the choice between supplying `at` and setting useQueue:true, leaving little to infer.

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

Deploy Server

Other Tools