Teamsbot

Retrieve the name, description, type, and archived state of the current verified Microsoft Teams channel, or a standard channel in the current team. The server verifies that the channel belongs to the current team. Set include_tags=true only for the current verified standard channel to discover one page of the team's tags. Copy a returned tag's mention_token verbatim into teamsbot.send_message to notify its members. For another tag page, pass tag_page.next_cursor as tags_cursor with include_tags=true. Tag discovery requires a non-guest member of the host team. This is unavailable in personal chats.

Discover file references on the exact verified Microsoft Teams message that started this turn.

Resolve one file identity copied from the current verified Microsoft Teams event. The server restricts the file to the bound chat user or exact channel.

Retrieve basic profile fields for a current-team member returned by teamsbot.list_channel_members. The server verifies the current Teams channel context. Copy the returned aad_object_id and name into a teamsbot.send_message user mention as <@user:AAD-OBJECT-ID|Display Name>. Never put member_id in a mention token. This is unavailable in personal chats.

List one bounded page of members in a standard Microsoft Teams channel returned by teamsbot.list_public_channels. Standard channels inherit the current team's roster. Use teamsbot.get_user_profile with a returned member ID for details. Each member's aad_object_id and name can be copied into a teamsbot.send_message user mention as <@user:AAD-OBJECT-ID|Display Name>. Never put member_id in a mention token. This is unavailable in personal chats.

List standard Microsoft Teams channels in the current verified team. Use a returned channel ID with teamsbot.read_public_channel, teamsbot.get_channel_info, or teamsbot.list_channel_members. The server chooses the tenant and team; provide only an opaque cursor returned by a prior listing. This is unavailable in personal chats.

Move or rename one file or folder returned by a channel-file action inside the current verified Microsoft Teams channel. The server resolves the channel and revalidates both handles; IDs, URLs, cross-drive moves, and shortcuts are rejected. Provide a new name, a destination folder handle, or both.

Prepare a requester interaction.

Present requester card.

Present a server-owned safety review to the verified Teams requester.

Read and materialize the files directly inside the current verified Microsoft Teams channel folder or a folder returned by a channel-file action. Use this by default whenever the user asks to inspect, compare, analyze, or summarize files in a folder; do not call get_channel_file once per file. The server returns at most 20 permitted children and materializes permitted files up to 100 MB combined. Subfolders are returned as metadata but are not read recursively. Use only server-returned folder handles and cursors.

Read one bounded page of messages from the current verified Microsoft Teams channel when the user asks about recent channel context. Omit thread_root_message_id for top-level posts, or provide a returned root message ID to read that thread's replies. The server chooses the tenant, team, and channel; provide only the optional page size and an opaque cursor returned by a prior read. This is unavailable in personal chats.

Read one bounded page of top-level messages from a standard Microsoft Teams channel returned by teamsbot.list_public_channels. The server verifies that the channel belongs to the current team. This is unavailable in personal chats.

Read bounded context for the verified current Teams channel thread.

Remove a Microsoft Teams reaction from a trusted message in the invocation's verified destination. Provide only the exact trusted message ID and Teams reaction ID.

Render the complete current Teams task card.

Replace requester card.

Search for a specific file or folder beneath the current verified Microsoft Teams channel folder or a server-returned folder. Use a returned folder handle with read_channel_folder_files, or a returned file handle with get_channel_file. The server keeps the search inside the verified channel; never invent IDs or URLs.

Send an access-denial reply to the incoming Teams conversation before a task exists.

Send one native informative progress update for the verified Teams DM turn.

Send a Markdown text message as this assistant to Microsoft Teams. Use destination_id to select a conversation or channel thread. In a channel, mention a user with <@user:AAD-OBJECT-ID|Display Name>. For the requester, copy the trusted user_aad_object_id and user_display_name context fields exactly; do not invent a display label. For another user, use their verified Microsoft Entra user ID and display name. Never use the member_id field or legacy <@MEMBER-ID> syntax. To mention a tag in a standard channel, first call get_channel_info with include_tags=true and copy the exact returned mention_token (<@tag:GRAPH-TAG-ID|Tag Name>). Do not invent or re-encode tag IDs; use at most 10 tag mentions per message. Return web URLs as Markdown links (e.g., [label](https://example.com)).

Send a private targeted message to the current verified user inside a shared Microsoft Teams channel. Use portable Markdown for private text, or request the server-owned account connection prompt. This is unavailable in personal chats; never provide routing fields or URLs.

Show a temporary typing indicator while actively working on the current request. Call this before substantive work and again before additional long-running work if no Teams-visible response has been sent. Stop calling it once the final response is ready. If it fails, continue the task and still send the result.

Create a temporary working status for the verified Teams shared turn, or update the exact activity ID supplied by the trusted caller.

Replace the full contents of one existing file returned by a channel-file action in the current verified Microsoft Teams channel. The server resolves the exact channel and revalidates the handle; folders, shortcuts, IDs, and URLs are rejected. Use source_file for a runtime-provided or workspace file, or source_file_handle for a file returned by a current-channel file action. This does not structurally patch DOCX, PPTX, or XLSX files.

Upload a trusted runtime-provided file to the invocation's verified Microsoft Teams destination. Images render inline. Files use delegated Microsoft access; personal-chat files up to 20 MB fall back to Teams file consent when access is unavailable. Uploads go to the current channel folder, a selected server-issued channel folder, or the DM user's OneDrive ChatGPT folder. Use only a file reference supplied by the runtime; never invent or pass a URL.