Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Duplicate a scheduled post

duplicate_scheduled
Destructive

Copy a scheduled or published post into a new independent queued post to reuse creative or repost content. Override caption, media, channels, or schedule, or place it in the next free slot.

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.

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
linkNo
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.
titleNo
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
imageUrlNo
timezoneNoIANA zone for a wall-clock `at` or the queue
useQueueNoinstead of naming a time, take the brand’s next free posting slot
videoUrlNo
imageUrlsNoCAROUSEL — an ORDERED list of image URLs published as ONE swipeable post
locationIdNoGOOGLE BUSINESS — which listing (list_business_locations)
visibilityNo
linkedinOrganizationIdNoLINKEDIN — publish the copy as this company Page (list_linkedin_pages)

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. 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."
  3. 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."
  4. 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"
+}
  5. 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"
+}
  6. Addedv0.1.161

TDQS

A4.5/5.0
Behavior4/5

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

Adds substantial context beyond annotations: what is copied (caption, media, per-channel captions, title, description, tags, target board/Page/listing), that the copy is INDEPENDENT and editing/cancelling it never touches the original, and that it publishes even where the original already did. It does not explain what the destructiveHint=true annotation implies for this call, leaving a small 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 purpose and use cases, then the override/timing mechanics, then the independence caveat and the alternative. It is dense and slightly run-on, but each clause carries information an agent needs.

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?

Covers the core calling mechanics for a 21-parameter mutation well, including copy semantics and timing options. With no output schema, the description never says what comes back (e.g. a new post id), which is the main missing piece for an agent that may want to chain a follow-up call.

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?

With 76% schema coverage the schema already does heavy lifting, but the description adds real meaning: that any copied field can be overridden in the same call, that `at` names a new time or useQueue:true takes the brand's next free slot. Several parameters (link, imageUrl, videoUrl, visibility) remain undocumented in both places.

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 — copy an existing scheduled or published post into a NEW queued post — and immediately names the sibling it is not (retry_scheduled). The distinction from schedule_post and post_edit is implicit but clear from the copy semantics.

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 when-to-use scenarios (run a creative again, reuse a winner as a starting point, re-send after publish) and an explicit exclusion with routing: 'To re-fire only the channels that FAILED, use retry_scheduled instead.'

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