list_reply_inbox

mcp:readread-only

List the reply inbox: replies to and mentions of the user's X account (kind 'mention') and new posts from the accounts and keywords they watch (kind 'community'), each with a drafted reply (draftText) and a one-line reason. Reddit threads (platform 'reddit') are posts where someone describes the problem the user's product solves, found by Reddit listening, with a helpful reply that doesn't pitch; title and community (the subreddit) say where. status 'open' (default) is everything waiting on the user; 'sent' and 'dismissed' are done; platform filters to 'x' or 'reddit'; feedId to the posts one Engage feed found (feedId and matchedBy name the feed).

Show the user the post and the draft before doing anything with it. Mentions with canSendFromApp can be sent with send_reply once the user approves the exact text; X community posts, and Reddit threads without canSendFromApp, can't be sent from the app, so give the user replyOnXUrl (the X reply box or the Reddit thread) to post it themselves. Call refresh_reply_inbox to check X and Reddit for new ones.

Returns { items, page, limit, total, hasMore }: limit is per page (default 50, max 100), page is 1-based; call again with page + 1 while hasMore is true.

Input

• statusstring

  one of open, sent, dismissed, all · default "open"

• kindstring

  one of mention, community, all · default "all"

• platformstring

  one of x, reddit, all · default "all"

• feedIdstring

  min length 1 · max length 64

• pageinteger

  1-based page number. Use with limit; hasMore says whether another page exists.

  min 1 · default 1

• limitinteger

  min 1 · max 100 · default 50

Permission

Needs the mcp:read scope: view your workspace. It only reads, so assistants can call it without asking.

Example call

Your assistant sends this for you. It is shown so you can see the shape of a call, with placeholder values for the required fields.

tools/call

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

Same action over the REST API

The tool runs GET /v1/orgs/{orgId}/engagement as the signed-in user, with the same validation, approval rules and limits. See it in the Reply inbox API reference.