Skip to main content
Glama
Sign In

Postkey: Instagram DM Automation and Comment-to-DM

by pro.postkey
OverviewDiscussionsAdmin

Label a conversation

postkey_label_conversation
Idempotent

Postkey: Puts an Inbox label on one conversation or takes it off, and returns its labels. Labels are for the team only; the contact is not changed and nothing is sent. To tag the person themselves (seen on every conversation and in contacts) use postkey_tag_contact.

Input Schema

NameRequiredDescriptionDefault
onYestrue puts the label on, false takes it off.
labelYes"favorites" (every plan), "hot_leads" or "partnerships" (plans with all Inbox labels), or a custom label's id as shown in labels by postkey_get_conversation. 1 to 60 characters.
conversation_idYesThe conversation id from postkey_list_conversations (or conversation_id in postkey_get_contact), as it was given.

Output Schema

NameRequiredDescriptionDefault
okYesfalse: refused (isError; code, message, guide_topic, url); no change.
labelsNoThe conversation's labels now.
conversation_idNoThe conversation id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / ok / description
      Previous value: -"false: refused (isError true; code, message, guide_topic, url), nothing changed."New value: +"false: refused (isError; code, message, guide_topic, url); no change."
  2. Changed4 schema fields changed
    • changedInput schema / properties / conversation_id / description
      Previous value: -"The conversation id from postkey_list_conversations."New value: +"The conversation id from postkey_list_conversations (or conversation_id in postkey_get_contact), as it was given."
    • changedInput schema / properties / label / description
      Previous value: -"The label."New value: +"\"favorites\" (every plan), \"hot_leads\" or \"partnerships\" (plans with all Inbox labels), or a custom label's id as shown in labels by postkey_get_conversation. 1 to 60 characters."
    • changedInput schema / properties / on / description
      Previous value: -"true puts it on, false takes it off."New value: +"true puts the label on, false takes it off."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "conversation_id": {
+      "description": "The conversation id.",
+      "type": "string"
+    },
+    "labels": {
+      "description": "The conversation's labels now.",
+      "type": "array"
+    },
+    "ok": {
+      "description": "false: refused (isError true; code, message, guide_topic, url), nothing changed.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / conversation_id / pattern
      Previous value: -"^([0-9]{1,40}|[0-9a-f]{24})$"New value: +"^([0-9]{1,40}|[0-9a-f]{24}|[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12})$"
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true and openWorldHint=false, so the safety profile is partly covered. The description adds genuinely useful context beyond that: labels are internal to the team, the contact record is untouched, and no message is sent. It stops short of covering error cases or permission requirements, which keeps it at a 4 rather than a 5.

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?

Two short sentences, front-loaded with the action and followed by the scoping constraint and sibling routing. Every clause earns its place; there is no filler.

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?

With an output schema covering the returned labels, full annotations, and 100% schema coverage on all three required params, the description supplies everything an agent needs to choose and invoke this tool 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 100% — the schema already explains the on/off boolean, the allowed label values, and where conversation_id comes from. The description adds no parameter-level detail beyond that, so the baseline 3 applies.

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?

States a precise verb and resource — putting an Inbox label on one conversation or taking it off — and also notes it returns the labels. It explicitly distinguishes itself from postkey_tag_contact, so an agent can pick between the two without opening either schema.

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?

Gives both the condition for use here (team-only Inbox labels on a conversation) and the alternative path (postkey_tag_contact for tagging the person), plus the exclusion that the contact is not changed. Nothing is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Postkey: Instagram DM Automation and Comment-to-DM toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources