Skip to main content
Glama
Upload-Post

Upload-Post

Official
by Upload-Post
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Hide, like or pin a comment

comment_action

Moderate or react to comments on your own posts: hide, like, pin, approve, or edit across TikTok, Facebook, Instagram, YouTube, and Threads.

Instructions

Moderate or react to a comment on one of the profile's own posts. One endpoint for every network, chosen with platform; each network supports its own verbs and answers 400 platform_not_supported / invalid action otherwise. TikTok: hide/unhide (postId), like/unlike (no postId), pin/unpin (postId). Facebook: hide/unhide, like/unlike, edit (needs message). Instagram: hide/unhide a comment, or enable_comments/disable_comments on a post (postId, no commentId). YouTube: hide/unhide/hold (postId; banAuthor only with hide). Threads: hide/unhide, approve/ignore. Every action has an inverse, so nothing here is permanent. Deleting a comment is a different tool: delete_comment. 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.
actionYesWhat to do. Lowercase; each value already carries its direction, so there is no separate 'undo' flag. Which values a platform accepts is listed in the tool description.
postIdNoPost the comment belongs to (TikTok: the video id). Required for TikTok hide/unhide and pin/unpin, YouTube moderation and Instagram enable_comments/disable_comments; not used by like/unlike.
messageNoFacebook `edit` only: the new comment text.
platformYesSocial platform the comment lives on.
banAuthorNoYouTube `hide` only: also ban the comment's author from the channel.
commentIdNoComment to act on (from get_post_comments). Sent as `comment_id`. Required except Instagram enable_comments/disable_comments.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.11.4
    • changedInput schema / properties / action / description
      Previous value: -"What to do. Lowercase; each value already carries its direction, so there is no separate 'undo' flag."New value: +"What to do. Lowercase; each value already carries its direction, so there is no separate 'undo' flag. Which values a platform accepts is listed in the tool description."
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "hide",
-  "unhide",
-  "like",
-  "unlike",
-  "pin",
-  "unpin"
-]New value: +[
+  "hide",
+  "unhide",
+  "like",
+  "unlike",
+  "pin",
+  "unpin",
+  "edit",
+  "hold",
+  "approve",
+  "ignore",
+  "enable_comments",
+  "disable_comments"
+]
    • addedInput schema / properties / banAuthor
      Added value: +{
+  "description": "YouTube `hide` only: also ban the comment's author from the channel.",
+  "type": "boolean"
+}
    • changedInput schema / properties / commentId / description
      Previous value: -"Comment to act on (from get_post_comments). Sent as `comment_id`."New value: +"Comment to act on (from get_post_comments). Sent as `comment_id`. Required except Instagram enable_comments/disable_comments."
    • addedInput schema / properties / message
      Added value: +{
+  "description": "Facebook `edit` only: the new comment text.",
+  "type": "string"
+}
    • changedInput schema / properties / platform / enum
      Previous value: -[
-  "tiktok"
-]New value: +[
+  "tiktok",
+  "facebook",
+  "instagram",
+  "youtube",
+  "threads"
+]
    • changedInput schema / properties / postId / description
      Previous value: -"Post the comment belongs to (TikTok: the video id). Required for hide/unhide and pin/unpin; not used by like/unlike."New value: +"Post the comment belongs to (TikTok: the video id). Required for TikTok hide/unhide and pin/unpin, YouTube moderation and Instagram enable_comments/disable_comments; not used by like/unlike."
    • changedInput schema / required
      Previous value: -[
-  "user",
-  "platform",
-  "commentId",
-  "action"
-]New value: +[
+  "user",
+  "platform",
+  "action"
+]
  2. Addedv0.11.1

TDQS

A4.9/5.0
Behavior5/5

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

With annotations already declaring mutation (readOnlyHint=false) and non-destructive status (destructiveHint=false), the description adds key behavioral context: every action has an inverse so nothing is permanent, plus platform-specific auth requirements (TikTok 'comments' capability, reconnect requirement) and error responses. This goes well beyond the structured annotations.

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?

The description is front-loaded with the general purpose and then organized by platform, which is appropriate for the complexity. It is dense but every sentence serves a purpose; minor improvements could come from breaking the platform lists into a more scannable format, but it is not verbose.

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?

For a multi-platform moderation tool with 7 parameters and an output schema, the description covers when to use it, platform-specific actions, parameter constraints, auth prerequisites, error behavior, and reversibility. Nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema description coverage is 100%, the description adds cross-parameter semantics that the schema does not encode: per-platform action validity (e.g., TikTok like/unlike require no postId, Facebook edit needs message), the `banAuthor` restriction to YouTube hide, and the Instagram enable_comments/disable_comments exception for commentId. This meaningfully reduces trial-and-error.

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?

The description states a clear verb+resource ('Moderate or react to a comment') and immediately distinguishes it from siblings by naming `delete_comment` as the tool for deletion. It also clarifies that it is a single endpoint for multiple networks chosen via `platform`, so an agent can route correctly.

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 when-to-use guidance is given: it names the alternative (`delete_comment`) for deletion and details which platform supports which actions. It also explains the error behavior (`400 platform_not_supported`) and TikTok capability prerequisite, leaving no ambiguity about eligibility.

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