Skip to main content
Glama
Sign In
Upload-Post

Upload-Post

Official
by Upload-Post
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create a comment or reply

create_comment
Destructive

Post a top-level comment or reply on a social media post by specifying a post ID, post URL, or comment ID, with a preview step before confirmed publishing.

Instructions

Post a top-level comment or a reply on a post. Provide exactly ONE of commentId (reply to a comment), postId, or postUrl (top-level). LinkedIn: postId=the post urn. Instagram requires commentId (replies only). TikTok always needs postId (the video id); add commentId on top of it to reply inside that thread. X: links are removed from the message unless the account is allowed links on X (the response then lists it in warnings), and a message that was only links is refused with 400 x_links_not_allowed. Replies on X share a daily limit per X account with post edits and reposts made through Upload-Post (20 a day on the free plan, 200 on paid plans, reset at 00:00 UTC); past it the call returns 429 x_daily_write_limit with retry_after in seconds. TikTok: Requires the 'comments' capability on the profile's TikTok account (see the capabilities array in list_users). It is granted at connection time, so an account connected earlier has to reconnect TikTok before this works. 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.

Input Schema

NameRequiredDescriptionDefault
userYesUpload-Post profile name.
postIdNoTop-level comment on this post ID. LinkedIn: the post urn. TikTok: the video id, always required.
messageYesComment text to post.
postUrlNoTop-level comment on this post URL.
platformNoSocial platform. One of instagram, facebook, youtube, linkedin, tiktok, x, threads, bluesky.instagram
commentIdNoReply to this comment. Required by Instagram. TikTok: pass it together with postId to reply inside a thread.
confirmedNoSet to true only after the user has seen the preview this tool returns without it and approved it. Without it nothing is sent.

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.17.2
    • addedInput schema / properties / confirmed
      Added value: +{
+  "description": "Set to true only after the user has seen the preview this tool returns without it and approved it. Without it nothing is sent.",
+  "type": "boolean"
+}
  2. Changed2 schema fields changedv0.11.4
    • changedInput schema / properties / platform / description
      Previous value: -"Social platform. One of instagram, facebook, youtube, linkedin, tiktok."New value: +"Social platform. One of instagram, facebook, youtube, linkedin, tiktok, x, threads, bluesky."
    • changedInput schema / properties / platform / enum
      Previous value: -[
-  "instagram",
-  "facebook",
-  "youtube",
-  "linkedin",
-  "tiktok"
-]New value: +[
+  "instagram",
+  "facebook",
+  "youtube",
+  "linkedin",
+  "tiktok",
+  "x",
+  "threads",
+  "bluesky"
+]
  3. Changed6 schema fields changedv0.11.1
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / commentId / description
      Previous value: -"Reply to this comment. Required by Instagram."New value: +"Reply to this comment. Required by Instagram. TikTok: pass it together with postId to reply inside a thread."
    • changedInput schema / properties / platform / description
      Previous value: -"Social platform. One of instagram, facebook, youtube, linkedin."New value: +"Social platform. One of instagram, facebook, youtube, linkedin, tiktok."
    • changedInput schema / properties / platform / enum
      Previous value: -[
-  "instagram",
-  "facebook",
-  "youtube",
-  "linkedin"
-]New value: +[
+  "instagram",
+  "facebook",
+  "youtube",
+  "linkedin",
+  "tiktok"
+]
    • changedInput schema / properties / postId / description
      Previous value: -"Top-level comment on this post ID. LinkedIn: the post urn."New value: +"Top-level comment on this post ID. LinkedIn: the post urn. TikTok: the video id, always required."
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  4. Addedv0.7.0

TDQS

A4.6/5.0
Behavior5/5

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

Despite annotations already declaring destructiveHint and openWorldHint, the description adds substantial non-obvious behavior: X daily write limits with exact thresholds, 429 x_daily_write_limit plus retry_after, the 400 x_links_not_allowed refusal, link stripping surfaced in warnings, and TikTok capability-gating that requires reconnection. This is exactly the operational context annotations cannot convey.

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 exactly-one-of constraint, then layered platform notes and the safety protocol. Every clause carries real information, though the single dense paragraph makes the platform-specific rules harder to scan than a short bulleted structure would.

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?

An output schema exists, so return values need not be explained, and the description still calls out that preflight responses list stripped links in warnings. Combined with auth/capability requirements, error codes, and the two-step confirmation flow, an agent has everything needed to invoke this destructive, open-world tool correctly.

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%, so the baseline is 3, but the description earns above baseline by explaining platform-specific parameter interplay the schema only states per-field: 'TikTok always needs postId; add commentId on top of it to reply', and the mutual exclusivity of the three target parameters. It does not document the platform default or the user parameter's role, which keeps it from a 5.

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 and resource ('Post a top-level comment or a reply on a post') and immediately distinguishes the two modes via the exactly-one-of rule over commentId/postId/postUrl. An agent knows what the tool does and which shape of call it is making before reading the schema.

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 per-platform conditions (Instagram replies-only, TikTok needs postId plus optional commentId, X link restrictions) and a clear when-to-call protocol via the confirmed approval loop. The gap is sibling differentiation: reply_to_comment, public_reply_to_comment, and reply_to_google_business_review exist in the same family and the description never says why to pick this one over them.

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