RingCentral Chat

Call this first when the user asks what this RingCentral MCP server can do, what tools are available, or which RingCentral tasks are supported. Returns a concise overview of the RingCentral tool categories and representative tool names enabled for this endpoint.

about_ringcentral_mcp_tools

Resolve a RingCentral Team Chat person by exact person id, or by name, email, extension number, or phone number through the company directory. Returns a single resolved person for an exact match, a compact candidate list when the query is ambiguous, or not_found when nothing matches; it never guesses. personId, extensionId, email, extension number, and phone number are returned as distinct labeled fields and must not be treated as interchangeable. This tool does not perform administrative directory reads or user changes.

find_person

Create, update, or delete a RingCentral Team Chat Adaptive Card. Cards must be version 1.3 with only Action.OpenUrl and Action.Submit actions and meaningful fallbackText; other versions or actions are rejected before the request reaches RingCentral. Use ringex://team-chat/adaptive-cards/guide for the supported contract and ringex://team-chat/adaptive-cards/examples for the extended validated example catalog. Reading cards uses read_team_chat. Do not attach a card payload to a normal text post. This tool can delete content, so it is annotated as destructive.

manage_adaptive_card

Create an incoming webhook in a RingCentral Team Chat group, or activate, suspend, or delete an existing webhook. Reading webhooks uses read_team_chat. This tool includes a delete action, so it is annotated as destructive.

manage_incoming_webhook

Create, update, or delete a RingCentral Team Chat note, task, or event; publish/lock/unlock a note; or complete a task. Select resource and an action valid for it. For task.complete, taskId plus at least one of status, completenessPercentage, or assignees is required. Request status uses "Complete"/"Incomplete"; task reads use "Completed" for the completed state. Completion reads the task before and after the write to provide idempotency and verification. Reading these items otherwise uses read_team_chat. This tool includes delete actions, so it is annotated as destructive.

manage_chat_item

Update or delete an existing RingCentral Team Chat post. action:"update" replaces the post text; action:"delete" removes the post. Reading posts uses read_team_chat. This tool can delete content, so it is annotated as destructive.

manage_post

Create, update, archive, unarchive, delete, join, or leave a RingCentral Team Chat team; add or remove members; add or remove a chat from favorites; or update the company Everyone chat. Reading teams and chats uses read_team_chat. This tool includes archive, delete, and remove-members actions, so it is annotated as destructive.

manage_team

Read RingCentral Team Chat resources with a strict, discriminated input. Select a resource and action, then supply the required ids and filters. Use task/find with chatId and an exact subject, optionally assigneeId and status; it returns unique, ambiguous, not_found, or incomplete and never guesses. Use post/list_attachments to discover attachments in one bounded posts page. Use file/download with chatId, postId, and fileId from a readable post to return bounded file content as a native MCP image, audio, or embedded resource. This tool is strictly read-only and stays available even when write tools are disabled.

read_team_chat

Send a RingCentral Team Chat post, optionally with file or image attachments, to a known chat (chatId) or a resolved person (personId) for a direct chat. When a person is the destination the direct conversation is opened or reused first. Files are uploaded before the post is created. ChatGPT clients should supply one transformed file reference in file; clients that already have transformed references or exact standard base64 bytes can use files for additional attachments. The result reports the destination chat id, created post id, uploaded attachment ids, and per-step status so a failed post can be retried without re-uploading. Use find_person to resolve a person id first. To reply in a thread, pass threadId.

send_post