Messaging
Space MCP tools in the Messaging scope (messaging). Reach these with a wks_live_ key over space-mcp or space-api.
Tools in the messaging scope, callable over space-mcp (tools/call) or space-api (REST) with a wks_live_* key that grants messaging.
get_thread_messages
Scope: messaging:read
Get messages in a thread. Requires thread_id.
| Parameter | Type | Required | Description |
|---|---|---|---|
thread_id | string | yes | |
limit | number | ||
offset | number |
list_message_channels
Scope: messaging:read
List connected messaging channels (social DM accounts + shared PM) for this space.
list_message_threads
Scope: messaging:read
List inbox threads. Optional channel_id, platform, limit, offset.
| Parameter | Type | Required | Description |
|---|---|---|---|
channel_id | string | ||
platform | string | ||
limit | number | ||
offset | number |
request_help
Scope: messaging:run
Ask a human for hands-on help when you are blocked by something only a person can do: a login screen, a 2FA prompt, a CAPTCHA, a consent wall. Posts a card in the chat you're working in and notifies your owner; a person can then open your computer's Browser panel, take control, get past the blocker, and hand back — your waiting browser actions resume automatically. Use this INSTEAD of retrying a blocked step or asking for credentials in chat.
| Parameter | Type | Required | Description |
|---|---|---|---|
reason | string | yes | What you're blocked on, e.g. 'Login wall at the supplier portal — needs the account password and 2FA.' |
url | string | The page you're stuck at, if the blocker is a page. | |
what_to_do | string | What the person should do once they have the controls. |
request_permission
Scope: messaging:run
Ask for a permission you do NOT hold in this space, when a task needs it: a tool was refused with 'does not have permission to <action> <category>', or the thing you need is not in your tool list at all (see the list of what you lack below). Files a request; a card with Allow / Just once / No lands on your message in this chat, and the people who can answer are notified. Say in one line what you asked for and why, then WAIT and carry on with the part of the task you can do — never ask twice, never send anyone to a settings page. When it is answered you get a line in this chat: on 'allowed' retry the call (the tool is in your list now); 'allowed once' lasts an hour; on 'refused' work with what you have.
| Parameter | Type | Required | Description |
|---|---|---|---|
category | string | yes | The permission's category, as the refusal names it: contacts, tables, pages, communities, commerce, agent_mail, social… (see 'What you lack here'). |
action | read | write | run | delete | instructions | yes | read, write or run (delete / instructions only where a tool takes them). |
reason | string | yes | Why, in your own words — the person reads it on the card. e.g. 'You asked me to set up the members community; I can draft it but not open it.' |
task | string | The task you are on, one line. e.g. 'Setting up a members community for Studio'. | |
tool | string | The tool you wanted to call, if you know its name. |
send_message_reply
Scope: messaging:run
Reply / send a message in a thread (consequential). Requires thread_id and content.
| Parameter | Type | Required | Description |
|---|---|---|---|
thread_id | string | yes | |
content | string | yes | |
attachments | array |