Postkey: Instagram DM Automation and Comment-to-DM

List saved reply wording for X

postkey_x_list_templates

Read-onlyIdempotent

Postkey: Lists the customer's saved reply variants for X, optionally for one kind, with their names and text, and how many are recommended. Pick the text for postkey_x_check_before_send from these; change the set with postkey_x_save_templates. 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
`kind`	No	Only this kind. Leave out for both.

Output Schema

Name	Required	Description
`ok`	Yes	false: refused (isError; code, message, guide_topic, url); no change.
`count`	No	Variants returned.
`templates`	No	kind, name, text.
`usage_note`	No	Near the month's X allowance: pass on as it is.
`recommended`	No	How many to keep per kind.

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": {
+    "count": {
+      "description": "Variants returned.",
+      "type": "number"
+    },
+    "ok": {
+      "description": "false: refused (isError true; code, message, guide_topic, url), nothing changed.",
+      "type": "boolean"
+    },
+    "recommended": {
+      "description": "How many to keep per kind.",
+      "type": "object"
+    },
+    "templates": {
+      "description": "kind, name, text.",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "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.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the description's added value is the scope/authorization model: it acts under the customer's own X access, sends nothing to X, and full scope lives in postkey_x_status. That plus the connection-troubleshooting note is real behavioral context beyond the annotations, though it drifts into detail an agent listing variants does not strictly need.

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 and the two sibling references are front-loaded in the first sentence. The second half stacks multiple concerns — no-send guarantee, scope pointer, and reconnect instructions — which makes the definition longer than a one-parameter read tool warrants.

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?

An output schema exists so return values need not be explained, and the one optional enum param is covered. Auth and failure-mode context is present; the only gap is minor, since details about the X connection state are relevant mainly when the sibling tool 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 enum parameter is fully documented in the schema, so the baseline is 3. The description's 'optionally for one kind' restates the schema's 'Leave out for both' without adding format or semantics beyond it.

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 saved reply variants for X) plus the scope of what is returned — names, text, and recommended counts — and the optional kind filter. It is clearly distinguishable from postkey_x_save_templates (writes) and postkey_x_check_before_send (consumes the text).

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?

Explicitly routes the agent: use the returned text for postkey_x_check_before_send, and use postkey_x_save_templates to change the set. It also names the fallback path when postkey_x_check_before_send is unavailable (reconnect and tick the X consent option), so an agent knows what to do when this call's preconditions fail.

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?