Skip to main content
Glama
Sign In

Postkey: Instagram DM Automation and Comment-to-DM

by pro.postkey
OverviewDiscussionsAdmin

Unschedule a post

postkey_unschedule_post
Idempotent

Postkey: Takes a scheduled post off the schedule, or takes a post that waits for approval back out of Approvals. The post is kept as a draft. Use it before changing or deleting a scheduled post. A post that is already published cannot be unscheduled. To remove a draft for good use postkey_delete_post.

Input Schema

NameRequiredDescriptionDefault
post_idYesThe post id (a UUID) from postkey_list_posts or postkey_create_post.

Output Schema

NameRequiredDescriptionDefault
okYesfalse: refused (isError; code, message, guide_topic, url); no change.
noteNoWhat changed.
statusNoThe post's status after the save.
post_idNoThe post id.
warningsNoThings to fix before it can be sent.
unscheduledNotrue: it is a draft again.

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. Changed2 schema fields changed
    • changedInput schema / properties / post_id / description
      Previous value: -"The post id."New value: +"The post id (a UUID) from postkey_list_posts or postkey_create_post."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "note": {
+      "description": "What changed.",
+      "type": "string"
+    },
+    "ok": {
+      "description": "false: refused (isError true; code, message, guide_topic, url), nothing changed.",
+      "type": "boolean"
+    },
+    "post_id": {
+      "description": "The post id.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "status": {
+      "description": "The post's status after the save.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "unscheduled": {
+      "description": "true: it is a draft again.",
+      "type": "boolean"
+    },
+    "warnings": {
+      "description": "Things to fix before it can be sent.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, so the safety profile is covered. The description still adds real value beyond them: the resulting state is a draft, the operation is reversible in effect, and published posts are rejected. It stops short of covering error behavior or permissions, but the outcome disclosure is substantial.

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?

Front-loaded with the core action, then outcome, then the exclusion, then the sibling pointer – a sensible ordering with no filler. Four short sentences, all carrying information; nothing is redundant.

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?

For a one-parameter state-change tool with an output schema and full annotation coverage, nothing an agent needs is missing: trigger, precondition, resulting state, and the alternative for permanent removal are all stated.

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 post_id property already documents the UUID pattern and its source tools (postkey_list_posts, postkey_create_post). The description adds no further meaning about the identifier, so the schema does the work and 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 specific verb and resource ('takes a scheduled post off the schedule') and extends it to the approval-queue case, which an agent would not otherwise infer. It is clearly distinguishable from postkey_schedule_post and postkey_delete_post by the explicit routing sentence.

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 positive guidance ('use it before changing or deleting a scheduled post'), a hard exclusion ('a post that is already published cannot be unscheduled'), and an explicit alternative for the different intent ('to remove a draft for good use postkey_delete_post'). The agent can pick correctly without opening the schema.

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