Skip to main content
Glama
Upload-Post

Upload-Post

Official

Repost / forward a post

repost_post

Reshare a published post to LinkedIn, X, Threads, or Telegram. Preview it first, then confirm to send with a commentary, as a Page, or to a target chat.

Instructions

Reshare a published post. LinkedIn (reshare, optional commentary, target_linkedin_page_id to reshare as a Page), X (retweet), Threads (repost), Telegram (forward or copy a channel post into another chat). Telegram: mode forward (shows the source) or copy (no link back), target_chat_id (@username or id) or target_user (another Upload-Post profile with Telegram), post_ids for several messages, all_messages true to include the messages a long post was split into (rest of the caption, first comment). More Telegram fields in params: telegram_message_thread_id, telegram_disable_notification, telegram_protect_content, caption, telegram_remove_caption, telegram_reply_markup. Needs the user's approval: call it first without confirmed to get a preview (nothing is sent), show the user exactly what will go out, and repeat the call with confirmed: true only after they approve.

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": {
      "user": "<user>",
      "platform": "<platform>"
    },
    "name": "repost_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoTelegram only. Default forward.
userYesUpload-Post profile name that owns the post.
paramsNoOther API fields for this action, with the REST API's own names (snake_case) and shapes. Telegram extras listed in the description. Leave out what you do not want to change.
post_idNoThe post id on the platform. Telegram may use `post_ids` instead.
platformYes
post_idsNoTelegram only: several message ids (1-100) sent together.
confirmedNoSet to true only after the user has seen the preview this tool returns without it and approved it. Without it nothing is sent.
commentaryNoLinkedIn only: text added on top of the reshare.
target_userNoTelegram only: another Upload-Post profile whose Telegram chat receives it.
all_messagesNoTelegram only: also send every message the post was split into.
target_chat_idNoTelegram only: destination chat (@username or numeric id).
target_linkedin_page_idNoLinkedIn only: reshare as this organization Page.

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.25.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already flag this as a non-read-only, non-idempotent, open-world write, and the description adds real value on top: the two-step preview-then-confirm protocol (nothing is sent without `confirmed`), and the semantic difference between forward (shows the source) and copy (no link back). It does not describe rate limits, failure/retry behavior, or what the preview payload contains, which matters for a multi-platform send with no idempotency guarantee.

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?

Core purpose is front-loaded and every sentence carries platform-specific information, but the Telegram section is a dense parenthetical run-on that mixes required and optional fields. A short bulleted breakdown would scan better without losing content.

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?

With an output schema present, return values need not be explained, and the description covers the approval protocol, per-platform semantics, and the opaque `params` bag well. It is somewhat thinner on ordering/preconditions (e.g. whether the source post must be published, what happens if `confirmed` is sent with an invalid target).

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 92%, so the baseline is 3, but the description adds genuine meaning beyond the schema: it explains the forward-vs-copy consequence, what `all_messages` actually pulls in (rest of caption, first comment), and it enumerates Telegram extras that live only inside the untyped `params` bag (telegram_message_thread_id, telegram_protect_content, telegram_reply_markup, etc.). That last point is value the schema cannot provide.

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?

Opens with a specific verb+resource ("Reshare a published post") and then enumerates exactly what that means per platform: LinkedIn reshare, X retweet, Threads repost, Telegram forward/copy. An agent knows precisely what operation this performs and on which four platforms.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit conditional guidance for Telegram (forward vs copy, target_chat_id vs target_user, post_ids vs all_messages) and a mandatory approval workflow: call without `confirmed` for a preview, then repeat with `confirmed: true` only after the user approves. It stops short of naming sibling alternatives such as edit_post or post_action, so there is no explicit when-not-to-use statement.

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