Get the Social Inbox configuration
social_inbox.config.get
Returns the inbox configuration of the organization: sync_enabled (whether messages are being ingested; it is turned on from the screen) and enabled_at (since when), enabled_sources (source → false means that source is not ingested; absent means enabled), inbox_agent_uids (who can be assigned, what config.update calls agent_uids; absent means every member) with inbox_agents (those members with their names) and updated_at (0 when the configuration was never saved). Requires view access to the Social Inbox.
- Scope
social_inbox:read- Permission
- View the module
- MCP tool
social_inbox_config_getOn the full surface; on the compact one,mb_execute_operationwithid: "social_inbox.config.get".
Declared cost: up to 23 reads and 0 writes per call (they count against the daily quota).
Parameters
No parameters.
Response
sync_enabledbooleanWhether the inbox is on (it brings new comments and messages from the connected networks).
updated_atnumberLast change (epoch ms); 0 = the configuration was never saved.
enabled_atnumber | nullWhen the inbox was turned on (epoch ms).
enabled_sourcesobject | nullSource → false = not brought in (ig_comment, tt_message…). Absent or missing key = brought in.
inbox_agent_uidsarray<string> | nullThe members offered in the Assign menu (what config.update calls agent_uids). Absent = every member.
inbox_agentsarray<object>Those members with their names (only the ones still in the organization).
Errors
Example
curl "https://api.mb-suite.com/v1/social-inbox/config" \
-H "Authorization: Bearer $MB_API_KEY"Try it with your test API key
With a test API key the request always goes to your practice organization: example data you can reset.
curl "https://api.mb-suite.com/v1/social-inbox/config" \
-H "Authorization: Bearer $MB_TEST_KEY"