Skip to main content
Glama
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 to a comment on social media posts through Upload-Post. Provide a post ID, post URL, or comment ID.

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. 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.

Input Schema

TableJSON 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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+]
  2. 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#"
  3. Addedv0.7.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, openWorldHint=true, so safety is partly covered. The description adds real behavioral context beyond them: the TikTok 'comments' capability must exist on the profile, it is granted at connection time, and older connections must reconnect. It does not explain why destructiveHint is set or what the call affects irreversibly.

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 rule, then platform-specific deltas in compact clauses. Slight redundancy with the schema (e.g. 'LinkedIn: postId=the post urn' repeats the property description), but no wasted sentences overall.

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 described, and the annotations plus 100% schema coverage carry the rest. The description supplies the platform routing matrix and the permission caveat, making it nearly complete; only the relationship to overlapping reply siblings is unaddressed.

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. The description earns above baseline by adding cross-parameter conditional logic the schema states only in isolation: exactly-one-of commentId/postId/postUrl, LinkedIn postId as post urn, and TikTok requiring postId with commentId layered on for thread replies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Post a top-level comment or a reply on a post') and immediately splits the two modes of operation. However, it never differentiates itself from close siblings like reply_to_comment, public_reply_to_comment, or comment_action, which an agent could easily confuse with this tool.

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 a concrete selection rule ('Provide exactly ONE of commentId, postId, or postUrl') plus per-platform conditions: Instagram requires commentId, TikTok always needs postId, add commentId to reply in-thread. It lacks any explicit when-not or sibling-alternative guidance, which is the remaining gap.

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