Skip to main content
Glama
Upload-Post

Upload-Post

Official
by Upload-Post
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete a comment

delete_comment
Destructive

Delete a comment on Instagram, Facebook, YouTube, LinkedIn, or TikTok using its ID. For LinkedIn, also provide the post ID; TikTok requires the comments capability.

Instructions

Delete a comment by commentId. LinkedIn also requires postId (the post urn); TikTok needs only the commentId. 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.
postIdNoLinkedIn only: the post urn the comment belongs to.
platformNoSocial platform. One of instagram, facebook, youtube, linkedin, tiktok.instagram
commentIdYesID of the comment to delete.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.11.1
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • 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"
+]
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. Addedv0.7.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already mark destructiveHint=true and readOnlyHint=false, so the description adds useful context: the LinkedIn postId dependency, the TikTok capability requirement, and the fact that older connections must be reconnected. This goes beyond the annotations and informs the agent about potential failure conditions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three concise sentences, front-loading the primary action and then efficiently addressing platform-specific requirements. No redundant wording; each sentence adds necessary information.

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?

The tool has an output schema, so return details are not needed. The description covers the main prerequisites (postId for LinkedIn, TikTok capability) and the need for reconnection. It is sufficiently complete for an agent to execute the deletion correctly, though it doesn't detail behavior for other platforms, which is likely fine.

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 description coverage is 100% with clear per-parameter descriptions. The description adds value by explicitly clarifying that postId is only needed for LinkedIn and commentId is the core ID, reinforcing platform-specific usage and the TikTok capability prerequisite, which is not purely schema-level.

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 clearly states the verb 'Delete' and resource 'comment' by `commentId`. It distinguishes from sibling tools like get_post_comments, reply_to_comment, and create_comment by focusing on deletion. The platform-specific nuance is highlighted, making it unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear operational context (e.g., LinkedIn requires postId, TikTok requires a capability) but does not explicitly state when to use this tool vs. alternatives or mention exclusions. It implies usage by the nature of the action but lacks direct comparative guidance.

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