AdaptlyPost

List Inbox Mentions

list_inbox_mentions

Read-onlyIdempotent

List posts and comments that mention the account, newest first, on Facebook, Instagram, Threads, Bluesky and Mastodon. Page with cursor while hasMore is true. An account whose mentions show RECONNECT_REQUIRED in get_inbox_summary returns none until the user reconnects it in AdaptlyPost. The inbox syncs every 10 minutes per account; refresh_inbox asks for a sync now. Needs the inbox.read permission, which every role holds.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_inbox_mentions"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Items per page (default 25)
`since`	No	ISO 8601 date-time. Only items created on the platform at or after it; for conversations, only those with a message at or after it. Omit for items of any date
`cursor`	No	nextCursor from the previous page. Omit for the first page; nextCursor is null on the last page
`search`	No	Free text to search the items for
`statuses`	No	Only items with these inbox statuses. Omit for every status
`platforms`	No	Only these platforms
`accountIds`	No	Only these accounts, by the id from list_accounts. Omit for every account
`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, total, hasMore and nextCursor (null on the last page). Each mention is 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.

Changed9 schema fields changedNov 9, 2026

changedInput schema / properties / accountIds / description

Previous value: -"Only these accounts, by the id from list_accounts, up to 50. Omit for every account"New value: +"Only these accounts, by the id from list_accounts. Omit for every account"

changedInput schema / properties / limit / description

Previous value: -"Items per page, 1 to 100 (default 25)"New value: +"Items per page (default 25)"

changedInput schema / properties / search / description

Previous value: -"Free text to search for, up to 200 characters"New value: +"Free text to search the items for"

changedInput schema / properties / since / description

Previous value: -"ISO 8601 date-time; only items created on the platform at or after it"New value: +"ISO 8601 date-time. Only items created on the platform at or after it; for conversations, only those with a message at or after it. Omit for items of any date"

changedInput schema / properties / statuses / description

Previous value: -"Only these statuses: UNREAD, READ or DONE. Omit for all"New value: +"Only items with these inbox statuses. Omit for every status"

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

addedOutput schema / properties / result / properties

Added value: +{
+  "hasMore": {
+    "type": [
+      "boolean",
+      "null"
+    ]
+  },
+  "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"
+      }
+    ]
+  },
+  "nextCursor": {
+    "description": "Pass as `cursor` for the next page. Null on the last page",
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "total": {
+    "description": "Items matching the filters across every page",
+    "type": [
+      "number",
+      "null"
+    ]
+  }
+}

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

AddedNov 8, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Goes well beyond the readOnly/idempotent/non-destructive annotations by disclosing ordering, pagination contract, a 10-minute sync cadence per account, the exact failure mode for disconnected accounts (returns none, not an error), and the required permission. These are precisely the traits an agent needs to interpret empty results correctly.

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?

Four dense sentences, front-loaded with the core purpose and ordering before operational caveats; nothing is filler. The opening platform list is the one element that costs more than it earns, since it understates the schema's supported platforms.

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 an eight-parameter, zero-required read tool with a full output schema and rich annotations, the description covers what structured fields cannot: ordering, sync freshness, the reconnect failure mode, and permission requirements. An agent has enough to call it and to explain an empty page correctly.

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%, so limit, since, cursor, search, statuses, platforms, accountIds and workspaceId are already fully documented upstream. The description reinforces cursoring ('page with cursor while hasMore is true') but adds no new meaning for the filtering parameters, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List posts and comments that mention the account') plus ordering ('newest first'), which separates it from list_inbox_comments and list_inbox_conversations by implication. The caveat is the platform enumeration ('Facebook, Instagram, Threads, Bluesky and Mastodon'), which is narrower than the schema's platform enum and could mislead an agent about coverage.

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?

Gives concrete operating guidance: page with cursor while hasMore is true, treat RECONNECT_REQUIRED accounts as empty until reconnection, and use refresh_inbox when 10-minute sync staleness matters. It stops short of explicitly naming when to prefer this over list_inbox_comments or update_inbox_mentions_status, so it is strong context rather than a full when/when-not/alternative matrix.

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?