Skip to main content
Glama
Upload-Post

Upload-Post

Official
by Upload-Post
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Send a direct message

send_dm
Destructive

Send an Instagram DM to any recipient using a recipient ID from comments or DM conversations, through your connected Instagram profile.

Instructions

Send an Instagram DM to a recipient from a connected Upload-Post profile. Use a recipient_id returned by Instagram comments or DM conversation tools.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userYesUpload-Post profile name that owns the connected Instagram account.
buttonsNoUp to 3 web_url buttons rendered in the DM. Each item is { title, url }.
messageYesDM body to send.
platformYesDM platform. Currently only Instagram DMs are supported.
recipient_idYesInstagram recipient/commenter ID. Required by the Upload-Post API.

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.8/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 agent knows this is a mutating, potentially destructive action. The description adds the prerequisite of a connected Upload-Post profile and the source of recipient_id, but does not disclose other behavioral traits such as delivery semantics, rate limits, or irreversibility. Given the annotations cover the safety profile, the description adds some value but remains limited.

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 concise sentences, perfectly front-loaded with the primary action and resource, followed by the key prerequisite. There is no fluff or repetition of schema details. Every word adds value.

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 simple send operation with a full input schema and an existing output schema, the description covers the essential context: what it does, the required connection, and how to get the recipient. It does not elaborate on edge cases or error conditions, but for this tool's simplicity and the presence of annotations covering safety, it is complete enough.

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 100%, so each parameter is already documented. The description adds meaningful guidance on how to obtain recipient_id (from comments or DM tools) and implies that user should be a connected profile, but this is marginal over the schema. For a well-covered schema, baseline is 3, and the extra note is helpful but not comprehensive enough to raise the score.

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 action ('Send an Instagram DM'), the resource (recipient), and the context ('from a connected Upload-Post profile'). It also specifies how to obtain the critical recipient_id, making the tool's purpose immediate and unambiguous. There is no sibling that sends DMs, so it is easily distinguished.

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 guidance on the prerequisite for the recipient_id ('returned by Instagram comments or DM conversation tools'), which is necessary for correct usage. However, it does not explicitly say when to use this tool instead of alternatives like reply_to_comment or manage_autodms, nor does it mention any exclusions or conditions. The usage context is implied but not fully explicit.

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