Skip to main content
Glama
Sign In
Upload-Post

Upload-Post

Official
by Upload-Post
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Private reply (DM) to commenter

reply_to_comment
Destructive

Sends a private Instagram DM to the author of a comment within the 7-day reply window, with a preview and explicit user approval before sending.

Instructions

Send a private DM to the author of an Instagram comment (within Instagram's 7-day reply window). Needs the user's approval: call it first without confirmed to get a preview (nothing is sent), show the user exactly what will go out, and repeat the call with confirmed: true only after they approve.

Input 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
confirmedNoSet to true only after the user has seen the preview this tool returns without it and approved it. Without it nothing is sent.

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.17.2
    • addedInput schema / properties / confirmed
      Added value: +{
+  "description": "Set to true only after the user has seen the preview this tool returns without it and approved it. Without it nothing is sent.",
+  "type": "boolean"
+}
  2. 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#"
  3. 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"
+}
  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?

The description adds critical behavior beyond the annotations: calling without `confirmed` returns a preview and sends nothing, and `confirmed: true` should be used only after user approval. This directly clarifies the mutation and approval semantics of the tool.

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 two compact sentences with the core action and approval workflow front-loaded. There is no repetitive or unnecessary text.

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?

For a mutation tool with an output schema and annotations, the description covers the essential safety workflow and the 7-day window. It leaves some parameter semantics implicit, but the critical execution flow is complete enough for an agent to call it correctly.

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 description coverage is 50%, and the description mainly reinforces the `confirmed` workflow already documented in the schema. It does not explain the `user`, `commentId`, `message`, or `buttons` parameters beyond what is obvious from their names.

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. It distinguishes this from public comment replies by explicitly calling it a private DM, and the 7-day window adds useful scope.

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?

It gives a clear usage condition: the action must occur within Instagram's 7-day reply window. It also explains the required approval workflow, though it does not explicitly name sibling alternatives such as public_reply_to_comment or send_dm.

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