Skip to main content
Glama
Sign In

Postkey: Instagram DM Automation and Comment-to-DM

by pro.postkey
OverviewDiscussionsAdmin

What is waiting for approval

postkey_list_waiting_for_approval
Read-onlyIdempotent

Postkey: Lists what waits for a person: the posts in Posts > Approvals (only for a connection that may read posts), and this connection's own held calls (a reply, turning an automation on) with what became of each: waiting, approved, rejected, lapsed or failed (postkey_get_approval reads one by its request_id). Up to 25 of each. Use it to find out whether something you asked for was sent, before saying so or asking again; other posts are in postkey_list_posts.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
okYesfalse: refused (isError; code, message, guide_topic, url); no change.
posts_noteNoPresent instead of the posts when this connection may not read posts.
posts_waitingNoUp to 25 posts in Posts > Approvals: post_id, title, caption_start, planned, asked_at, asked_by.
your_requestsNoUp to 25 of this connection's held calls: request_id, tool, what (untrusted), status (waiting, approved, rejected, lapsed, failed), asked_at, answered_at, lapses_at, outcome.
untrusted_noteNoPresent when outside text is wrapped as { untrusted: true, text }.
approve_in_postkeyNoWhere a person approves.
posts_waiting_countNoAll posts waiting.

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 / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "approve_in_postkey": {
+      "description": "Where a person approves.",
+      "type": "string"
+    },
+    "ok": {
+      "description": "false: refused (isError true; code, message, guide_topic, url), nothing changed.",
+      "type": "boolean"
+    },
+    "posts_note": {
+      "description": "Present instead of the posts when this connection may not read posts.",
+      "type": "string"
+    },
+    "posts_waiting": {
+      "description": "Up to 25 posts in Posts > Approvals: post_id, title, caption_start, planned, asked_at, asked_by.",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "posts_waiting_count": {
+      "description": "All posts waiting.",
+      "type": "number"
+    },
+    "untrusted_note": {
+      "description": "Present when outside text is wrapped as { untrusted: true, text }.",
+      "type": "string"
+    },
+    "your_requests": {
+      "description": "Up to 25 of this connection's held calls: request_id, tool, what (untrusted), status (waiting, approved, rejected, lapsed, failed), asked_at, answered_at, lapses_at, outcome.",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive profile, but the description adds genuinely new behavior: a hard cap of 25 items of each kind, permission-gated visibility, and the full outcome vocabulary (waiting, approved, rejected, lapsed, failed). It stops short of saying whether more than 25 can be retrieved or how to page past the cap, which is the remaining ambiguity.

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 statement and free of filler, but it is one long sentence threaded with nested parentheses that an agent must parse carefully. Splitting the state vocabulary and the alternative-tool routing into separate sentences would read more cleanly without adding length.

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?

An output schema exists, so return-shape explanation is unnecessary, and the description still characterizes the key result fields (the held request and its outcome state). For a zero-parameter read with annotations and an output schema, nothing an agent needs before calling is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing to disambiguate and the baseline of 4 applies. The description still usefully routes the request_id concept to the sibling tool that consumes it, which is helpful orientation rather than parameter documentation.

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 two-part resource explicitly: the posts sitting in Posts > Approvals plus this connection's own held calls (replies, automation toggles), each with its resulting state. It also distinguishes itself by name from postkey_get_approval (single record by request_id) and postkey_list_posts (everything else), so an agent can separate it from siblings 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete decision rule: use it to check whether something you asked for was sent, before claiming so or re-asking. It also names the alternative for single-record lookup and the alternative for non-approval posts, plus the precondition that post visibility only applies to a connection that may read posts.

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