Skip to main content
Glama
Sign In
Upload-Post

Upload-Post

Official
by Upload-Post
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get post comments

get_post_comments
Read-only

List comments on a social post by platform and post ID or URL; add commentId to retrieve replies under a specific comment.

Instructions

List comments on a post. One endpoint for every network, chosen with platform. Identify the post by either postId or postUrl (YouTube: postId=videoId; LinkedIn: postId=the post urn; TikTok: postId=the video id, postUrl is not accepted). Add commentId to get the REPLIES hanging off that one comment instead of the post's top-level comments — replies are the same question with one more parameter, not another tool. Reads are cached for up to 60 seconds (up to 2 minutes on X); a comment created or deleted through Upload-Post by the same account shows up on the next read. 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

NameRequiredDescriptionDefault
userYesUpload-Post profile name.
afterNoPagination cursor returned by a previous call.
limitNoComments to return (1-50; that ceiling is both Meta's and TikTok's).
postIdNoPlatform media/post ID. YouTube: the videoId. LinkedIn: the post urn. TikTok: the video id (required — TikTok has no URL lookup).
postUrlNoPublic URL of the post.
platformNoSocial platform. One of instagram, facebook, youtube, linkedin, tiktok, x, threads, bluesky.instagram
commentIdNoReturn the replies under this comment instead of the post's top-level comments. Sent as `comment_id`.

Output 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. Changed7 schema fields changedv0.11.1
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / commentId
      Added value: +{
+  "description": "Return the replies under this comment instead of the post's top-level comments. Sent as `comment_id`.",
+  "type": "string"
+}
    • changedInput schema / properties / limit / description
      Previous value: -"Comments to return (1-50, Meta's cap)."New value: +"Comments to return (1-50; that ceiling is both Meta's and TikTok's)."
    • changedInput schema / properties / platform / description
      Previous value: -"Social platform. One of instagram, facebook, youtube, linkedin. TikTok is unsupported."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: -"Platform media/post ID. YouTube: the videoId. LinkedIn: the post urn."New value: +"Platform media/post ID. YouTube: the videoId. LinkedIn: the post urn. TikTok: the video id (required — TikTok has no URL lookup)."
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  3. Changed3 schema fields changedv0.7.0
    • changedInput schema / properties / platform / description
      Previous value: -"Social platform. Only 'instagram' is currently supported."New value: +"Social platform. One of instagram, facebook, youtube, linkedin. TikTok is unsupported."
    • addedInput schema / properties / platform / enum
      Added value: +[
+  "instagram",
+  "facebook",
+  "youtube",
+  "linkedin"
+]
    • changedInput schema / properties / postId / description
      Previous value: -"Platform media/post ID."New value: +"Platform media/post ID. YouTube: the videoId. LinkedIn: the post urn."
  4. First observedv0.4.0

TDQS

A4.4/5.0
Behavior5/5

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

Goes well past the annotations: discloses 60-second caching (2 minutes on X), read-after-write behavior for comments created/deleted through Upload-Post, and a hard TikTok capability gate with a remediation path. These are exactly the operational facts that cause failed calls or stale-data confusion.

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-loads purpose, then identity rules, then the replies hint, then caching and the TikTok gate — a sensible priority order. The TikTok prerequisite is worth its length, though the platform-syntax parenthetical partially duplicates the schema.

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?

Covers what the output schema cannot: caching latency, eventual consistency, per-platform ID conventions, the cursor-based pagination entry point, and the one platform-specific authorization gotcha. Nothing essential for a correct first call is missing.

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. The description restates the postId-per-network mapping and the TikTok no-URL rule, which the schema already documents verbatim in its property descriptions. It adds the unifying frame (one endpoint, choose with `platform`) but no new parameter semantics.

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+resource ("List comments on a post") and immediately scopes it as a cross-network endpoint parameterized by `platform`. It also pre-empts the most likely confusion by declaring that replies are a parameter of this tool, not a separate 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 explicit when-to-use guidance for `commentId` (replies vs top-level) and a concrete prerequisite for TikTok (the 'comments' capability, granted at connect time, reconnect required). It does not point to write-side siblings such as reply_to_comment, but for a read tool the selection risk is low.

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