Inline

Create a private Inline thread containing you and the resolved participants, address them with named mentions, send one question, and return its receipt and replay cursor. This tool does not register Events or wait. Before an ask-and-wait send, establish host continuation support (ChatGPT Work or dots); regular ChatGPT chats require disclosing the limitation and accepting send-only. Use the host Events mechanism, which may be an Automations event trigger; events/subscribe is an MCP protocol method, not an Inline tool name. If the host accepts a replay cursor, use the returned cursor exactly. Otherwise register the exact message.created arguments, obtain host acknowledgement, then make one bounded messages.context read from the confirmed question messageId (before: 0, after: 50, includeAnchor: false, content: all) to check pre-registration replies. Disclose limited coverage if the read fails or fills its window; do not poll. Deduplicate overlapping replies by chatId/messageId and deliveries by eventId. Wait only after host registration, then read current context and continue the originating task. Stop this task's registration when a one-shot consultation is fulfilled. Creation and delivery are not idempotent; retain the chat ID and inspect uncertain outcomes before retrying.

conversations.ask

Use this tool to create a new Inline thread/chat in an allowed space or home threads. The audience follows the selected context: public threads in public spaces can be visible to anyone who joins. After creation, use messages.send or messages.send_batch with the returned chat.chatId.

conversations.create

Create a child of one resolved parent chat. The child inherits root-chat access plus its own direct/group grants. Participants added only to an intermediate child are not automatically inherited by descendants. participantUserIds adds access to a new child and cannot restrict root-chat access. Omit parentMessageId for an independent child, or supply it to create or reuse the reply thread for that message. An existing reply thread is returned without changing its title, description, emoji, or participants; these inputs apply only to new creation. Newly created private children include the creator directly; reuse does not repair older creator membership. Children outside spaces require home thread access. Use the returned chat.chatId for reading, sending, or forwarding.

conversations.create_subthread

Forward selected messages from a resolved source chat to a separately resolved destination chat, preserving the input order and media. Both chats must be approved by this grant. Resolve source and destination independently and inspect selected messages before forwarding. Returns ordered source/destination message ID pairs. Sending is not atomic or idempotent: an error may follow partial delivery, so inspect the destination before retrying to avoid duplicates. Forwarding headers follow server policy even when requested.

messages.forward

Return the Inline profile represented by this request's authenticated connection. The immutable user ID is stable across token refresh, reconnection, scope upgrades, and name or email changes.

account.profile

Use this tool after resolving a chatId to inspect conversation metadata, direct participants, explicit group-grant count, pinned message IDs, and parent/thread details before reading or sending. DMs also use chatId. Direct participants and group-grant count do not enumerate group members or inherited root-chat access and are not a complete audience list.

conversations.get

Use this tool when you need to inspect the current Inline MCP authorization, granted scopes, and allowed chat contexts before choosing read/write tools.

account.me

Use this tool after messages.search, messages.unread, or a known message ID to fetch a before/after window around that message in one chat. DMs also use chatId. Use messages.list for the latest context when there is no anchor message.

messages.context

Use this tool to extract file and media metadata from 1-20 known message IDs in one chat. Use messages.list with a files or media content filter first when message IDs are not known. DMs also use chatId.

files.get

Read exact message IDs from one resolved chat, including a DM. Results follow the requested order, with duplicate requests collapsed and unavailable IDs listed in missingMessageIds. Use this to inspect a selection before forwarding or verify known delivery receipts; use messages.context for surrounding discussion.

messages.get