AdaptlyPost

Mark Inbox Mentions

update_inbox_mentions_status

Idempotent

Mark a batch of mentions as unread, read or done in the AdaptlyPost inbox. Only AdaptlyPost changes; nothing is sent to the platform. Needs the inbox.reply permission, which Admin and Editor hold (403 permission_denied otherwise), and an active plan.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ids": "<ids>",
      "status": "<status>"
    },
    "name": "update_inbox_mentions_status"
  }
}

Input Schema

Name	Required	Description
`ids`	Yes	Ids of the mentions to mark, from list_inbox_mentions
`status`	Yes	Inbox status to give every listed item
`workspaceId`	No	Workspace to act in: an id from list_workspaces. Omit to act in the workspace list_workspaces marks current. Use the same workspaceId for every call about the same workspace, since ids from one workspace (accounts, posts, uploads) do not exist in another

Output Schema

Name	Required	Description	Default
`result`	Yes	An object with mentions (the updated mentions) and unreadCount. An InboxMention: id, accountId, platform, accountName, platformMentionId, author { id, name, username, avatarUrl }, text, permalink, thumbnailUrl, createdAt, status, replied, repliedAt, capabilities { canReply } and replies (each { id, text, permalink, createdAt }).

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 9, 2026

changedInput schema / properties / ids / description

Previous value: -"1 to 100 mention ids from list_inbox_mentions"New value: +"Ids of the mentions to mark, from list_inbox_mentions"

changedInput schema / properties / status / description

Previous value: -"UNREAD, READ or DONE"New value: +"Inbox status to give every listed item"

addedOutput schema / properties / result / additionalProperties
```
Added value: +true
```

addedOutput schema / properties / result / properties

Added value: +{
+  "mentions": {
+    "anyOf": [
+      {
+        "items": {
+          "additionalProperties": true,
+          "properties": {
+            "accountId": {
+              "description": "The account `id` from GET /social-accounts",
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "accountName": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "author": {
+              "anyOf": [
+                {
+                  "additionalProperties": true,
+                  "properties": {
+                    "avatarUrl": {
+                      "type": [
+                        "string",
+                        "null"
+                      ]
+                    },
+                    "id": {
+                      "description": "The platform user id",
+                      "type": [
+                        "string",
+                        "null"
+                      ]
+                    },
+                    "name": {
+                      "type": [
+                        "string",
+                        "null"
+                      ]
+                    },
+                    "username": {
+                      "type": [
+                        "string",
+                        "null"
+                      ]
+                    }
+                  },
+                  "type": "object"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "capabilities": {
+              "anyOf": [
+                {
+                  "additionalProperties": true,
+                  "properties": {
+                    "canReply": {
+                      "type": [
+                        "boolean",
+                        "null"
+                      ]
+                    }
+                  },
+                  "type": "object"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "createdAt": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "id": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "permalink": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "platform": {
+              "description": "One of: FACEBOOK, INSTAGRAM, THREADS, TIKTOK, TWITTER, BLUESKY, LINKEDIN, PINTEREST, YOUTUBE, MASTODON, TELEGRAM, GOOGLE_BUSINESS, TUMBLR, WORDPRESS",
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "platformMentionId": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "replied": {
+              "type": [
+                "boolean",
+                "null"
+              ]
+            },
+            "repliedAt": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "replies": {
+              "anyOf": [
+                {
+                  "items": {
+                    "additionalProperties": true,
+                    "properties": {
+                      "createdAt": {
+                        "type": [
+                          "string",
+                          "null"
+                        ]
+                      },
+                      "id": {
+                        "type": [
+                          "string",
+                          "null"
+                        ]
+                      },
+                      "permalink": {
+                        "type": [
+                          "string",
+                          "null"
+                        ]
+                      },
+                      "text": {
+                        "type": [
+                          "string",
+                          "null"
+                        ]
+                      }
+                    },
+                    "type": "object"
+                  },
+                  "type": "array"
+                },
+                {
+                  "type": "null"
+                }
+              ],
+              "description": "Replies sent from AdaptlyPost, oldest first"
+            },
+            "status": {
+              "description": "One of: UNREAD, READ, DONE",
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "text": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "thumbnailUrl": {
+              "type": [
+                "string",
+                "null"
+              ]
+            }
+          },
+          "type": "object"
+        },
+        "type": "array"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "unreadCount": {
+    "description": "Unread items of this channel left in the workspace",
+    "type": [
+      "number",
+      "null"
+    ]
+  }
+}

addedOutput schema / properties / result / type
```
Added value: +"object"
```
addedOutput schema / required
```
Added value: +[
+  "result"
+]
```

AddedNov 8, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive and closed-world, so the safety profile is covered; the description goes beyond that by disclosing the required permission (inbox.reply, held by Admin and Editor), the 403 permission_denied failure mode, the active-plan prerequisite, and the fact that the mutation is local to AdaptlyPost only. It stops short of saying what happens to ids that do not exist or whether the whole batch is atomic.

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

Conciseness5/5

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

Two sentences, front-loaded with the action and the value set, followed by scope and prerequisites. Nothing is repeated from the schema and no sentence is wasted.

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?

With an output schema present the description need not explain return values, and it covers scope, permissions, idempotent batch semantics and prerequisites. The remaining gap is edge-case behavior for invalid or cross-workspace ids, which matters given workspaceId scoping but is not addressed.

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 description coverage is 100%, including a documented enum for status and provenance notes for ids and workspaceId, so the schema carries the parameter meaning. The description adds only the batch framing and the status vocabulary, which the enum already supplies; 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 ("Mark") plus the resource ("mentions") and the exact value set (unread, read, done) in the AdaptlyPost inbox, and the batch framing matches the ids array. The resource word "mentions" alone separates it from the sibling update_inbox_comments_status / conversations_status / reviews_status tools without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

"Only AdaptlyPost changes; nothing is sent to the platform" implicitly contrasts this with reply_to_inbox_mention, which does send to the platform, and the permission sentence tells the agent when the call will fail. But no alternative is ever named and no explicit "use X instead when..." rule is given, so selection still requires inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AdaptlyPost 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?