Skip to main content
Glama
Sign In

Postkey: Instagram DM Automation and Comment-to-DM

by pro.postkey
OverviewDiscussionsAdmin

Get one DM automation

postkey_get_automation
Read-onlyIdempotent

Postkey: Gets one DM automation in full: its status, made_with, what starts it, the Instagram accounts it runs on, whether only followers get the link (followers_only), whether it has changes that are not published yet, its messages in order and, for a Quick form, its keywords, link and message texts. Each message has a step number: postkey_update_automation messages uses it to rewrite a Flow Builder automation's words. Use it before postkey_update_automation or postkey_publish_automation. Results are in postkey_get_automation_stats. An unknown id is refused not_found. An X reply automation also has replies_preview, daily_ceiling and x_status. A DM one also has delivery and dms.

Input Schema

NameRequiredDescriptionDefault
automation_idYesThe automation id (a UUID) from postkey_list_automations or postkey_create_automation.

Output Schema

NameRequiredDescriptionDefault
okYesfalse: refused (isError; code, message, guide_topic, url); no change.
automationNoThe list fields plus runs_on (instagram, status), followers_only, messages (step, kind, says, buttons, cards) and, for a Quick form, quick_form (keywords, opening_message, link_message, link_url).

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. Changed1 schema field changed
    • changedOutput schema / properties / automation / description
      Previous value: -"The list fields plus runs_on (instagram, status), followers_only, messages (step, kind, says, buttons) and, for a Quick form, quick_form (keywords, opening_message, link_message, link_url)."New value: +"The list fields plus runs_on (instagram, status), followers_only, messages (step, kind, says, buttons, cards) and, for a Quick form, quick_form (keywords, opening_message, link_message, link_url)."
  3. Changed2 schema fields changed
    • changedInput schema / properties / automation_id / description
      Previous value: -"The automation id from postkey_list_automations."New value: +"The automation id (a UUID) from postkey_list_automations or postkey_create_automation."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "automation": {
+      "description": "The list fields plus runs_on (instagram, status), followers_only, messages (step, kind, says, buttons) and, for a Quick form, quick_form (keywords, opening_message, link_message, link_url).",
+      "type": "object"
+    },
+    "ok": {
+      "description": "false: refused (isError true; code, message, guide_topic, url), nothing changed.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}
  4. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, non-destructive), yet the description still adds behavior beyond them: an unknown id is refused with not_found, response shape varies by automation type (X reply vs DM), the step number is the handle used by the update tool, and unpublished-change state is surfaced. Auth requirements and size limits are not mentioned, keeping it just short of the top band.

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

Conciseness4/5

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

Purpose is front-loaded and the trailing short sentences (workflow order, error behavior, type-specific fields) are each informative. The opening sentence is an overlong run-on list of fields, but nearly every clause carries decision-relevant 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?

Given a single-parameter read tool with annotations and an output schema, the description covers the essential gaps: error behavior, workflow preconditions, and conditional fields by automation type. Enumerating individual return fields is partially redundant with the output schema, but nothing an agent needs in order to call it correctly is missing.

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 coverage is 100% and the single parameter's description already specifies the UUID format and its source (postkey_list_automations or postkey_create_automation). The description adds no extra meaning about automation_id beyond what the schema provides, so it sits at the baseline.

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?

Opens with a specific verb and resource ('Gets one DM automation in full') and immediately enumerates what 'in full' means: status, made_with, trigger, accounts, followers_only, unpublished changes, ordered messages, plus Quick-form specifics. 'One' plus 'in full' contrasts with the list and stats siblings, so an agent can distinguish it without opening a schema.

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?

Explicitly states the workflow position: 'Use it before postkey_update_automation or postkey_publish_automation' and routes metrics requests to postkey_get_automation_stats. It does not state a when-not condition (e.g., use postkey_list_automations to discover ids), but the positive guidance is concrete and names real alternatives.

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