Skip to main content
Glama
Upload-Post

Upload-Post

Official
by Upload-Post
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Private reply (DM) to commenter

reply_to_comment
Destructive

Send a private DM to an Instagram comment author within the 7-day reply window, turning public comments into direct conversations.

Instructions

Send a private DM to the author of an Instagram comment (within Instagram's 7-day reply window).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userYes
buttonsNoUp to 3 web_url buttons rendered in the DM. Each item is { title, url }.
messageYes
platformNoSocial platform. Only 'instagram' is currently supported.instagram
commentIdYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.11.1
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. Changed1 schema field changedv0.7.0
    • addedInput schema / properties / buttons
      Added value: +{
+  "description": "Up to 3 web_url buttons rendered in the DM. Each item is { title, url }.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "title": {
+        "type": "string"
+      },
+      "url": {
+        "format": "uri",
+        "type": "string"
+      }
+    },
+    "required": [
+      "title",
+      "url"
+    ],
+    "type": "object"
+  },
+  "maxItems": 3,
+  "type": "array"
+}
  3. First observedv0.4.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the destructive, side-effecting nature is known. The description adds the 7-day reply window constraint, which is useful behavioral context, but it doesn't describe other consequences like irreversibility or on-behalf-of behavior. With annotations carrying the safety signal, this is adequate.

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?

One concise sentence front-loads the core action and the time constraint. No redundant words or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having an output schema, the tool's call structure remains unclear because required parameter semantics are undocumented. Critically missing: the role of the 'user' parameter (e.g., Instagram username? comment author handle?), how 'commentId' relates to comments, and how to discover valid 'commentId' values via sibling tools like get_post_comments. A minimal description does not fully equip an agent for correct invocation.

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

Parameters2/5

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

Schema description coverage is only 40%; 'buttons' and 'platform' are documented, but required params 'user', 'commentId', and 'message' have no descriptions. The description does not explain what 'user' means in this context, how to obtain 'commentId', or what content 'message' should contain, so agents are left to guess on critical inputs.

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 specific verb and resource: 'Send a private DM to the author of an Instagram comment.' The '7-day reply window' narrows context, and the title plus sibling names (public_reply_to_comment, send_dm) make the tool's unique purpose immediately distinguishable.

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?

The description gives clear context by specifying the 7-day reply window and implies the intended use is private replies rather than public ones. However, it does not explicitly mention alternative tools such as public_reply_to_comment or send_dm, nor does it say when not to use this tool.

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