Skip to main content
Glama
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 using postId or postUrl; add commentId to fetch 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. 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.
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

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. 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.8/5.0
Behavior5/5

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

Annotations already declare a safe read (readOnlyHint=true, destructiveHint=false), and the description layers on operationally important behavior: a per-platform capability gate, the fact that the capability is granted at connection time, and that previously connected TikTok accounts must reconnect. That is real disclosure beyond the annotation set.

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 the core purpose and then layers platform specifics and the precondition. Dense and mostly earning its sentences, though the parenthetical per-platform ID mapping restates schema text and slightly lengthens the block.

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?

With an output schema present, return values need no explanation, and the description covers the remaining gaps an agent needs: identifier selection, reply mode, pagination cursor, result ceiling, platform enum usage, and the TikTok capability prerequisite.

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 adds cross-parameter meaning: it frames `postId`/`postUrl` as mutually alternative identifiers and explains that `commentId` repurposes the whole call to return replies rather than post-level comments. Some per-platform detail (YouTube videoId, LinkedIn urn) duplicates the schema, so it is an increment rather than a full rewrite.

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 ('List comments on a post') and clarifies that it is one unified endpoint across networks selected by `platform`. It also distinguishes the reply-retrieval mode from siblings by noting replies are 'the same question with one more parameter, not another tool,' which separates it from create_comment/reply_to_comment.

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?

Explicit routing rules: identify the post by `postId` or `postUrl`, with a stated exclusion (TikTok does not accept `postUrl`), and explicit rules for when to add `commentId` to switch from top-level comments to replies. It also gives a prerequisite (TikTok 'comments' capability) and the remedy for accounts lacking it (reconnect).

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