Postkey: Instagram DM Automation and Comment-to-DM

List the X STOP list

postkey_x_list_stop

Read-onlyIdempotent

Postkey: Lists this profile's X STOP list: how many people are on it, and up to 200 of their hashes with when and how each was added. Postkey keeps no handles or names, only hashes, so to test one person pass their id to postkey_x_check_before_send. Sends nothing to X and no X send tool exists: act with the customer's own X access (full scope: postkey_x_status). If postkey_x_check_before_send is not available, this connection was not given X access; the person can reconnect and tick "X: ask Postkey before my agent replies".

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`ok`	Yes	false: refused (isError; code, message, guide_topic, url); no change.
`note`	No	How to read the hashes.
`count`	No	People on the STOP list.
`shown`	No	Rows returned (at most 200).
`contacts`	No	contact_hash, source, added_at.
`usage_note`	No	Near the month's X allowance: pass on as it is.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 9, 2026

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."

Changed1 schema field changedOct 24, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "contacts": {
+      "description": "contact_hash, source, added_at.",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "count": {
+      "description": "People on the STOP list.",
+      "type": "number"
+    },
+    "note": {
+      "description": "How to read the hashes.",
+      "type": "string"
+    },
+    "ok": {
+      "description": "false: refused (isError true; code, message, guide_topic, url), nothing changed.",
+      "type": "boolean"
+    },
+    "shown": {
+      "description": "Rows returned (at most 200).",
+      "type": "number"
+    },
+    "usage_note": {
+      "description": "Near the month's X allowance: pass on as it is.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}

First observedOct 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, but the description adds real context beyond them: only hashes are stored (no handles or names), the list is capped at 200 entries, nothing is sent to X, and the agent is told to act with the customer's own access. The access prerequisite and reconnect guidance are also disclosed.

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?

The purpose is front-loaded, and most of the length is justified by privacy limits, no-send behavior, and access prerequisites. The final sentence about reconnecting is somewhat verbose for a zero-parameter list tool, but it remains useful operational context.

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 zero-parameter, read-only listing tool with an output schema and full annotation coverage, the description is complete. It covers scope, return shape at a high level, privacy constraints, and the sibling needed to check an individual.

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?

This tool has zero parameters, so there is no parameter semantics to explain; the baseline is 4. The description does not pretend otherwise and adds relevant behavior around the returned hashes instead.

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: lists this profile's X STOP list, including the count and up to 200 stored hashes with when and how each was added. That is clearly distinguishable from siblings such as postkey_x_add_stop, postkey_x_remove_stop, and postkey_x_check_before_send.

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?

Routes the agent to postkey_x_check_before_send when testing one person, and explains that a missing check tool means the connection lacks X access. It does not spell out a 'when not to use' case, but the surrounding context makes the intended use clear.

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 tools Inspect

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

Need Help?