Skip to main content
Glama
mdwsk88

MS 365-21V MCP Server

by mdwsk88
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List Teams Chat Messages

teams_list_chat_messages
Read-only

Read messages from a Microsoft Teams chat as plain text, with sender, mentions, files, date filters, and cursor paging for older messages.

Instructions

Read messages in a Teams chat as plain text, oldest first within a page, with sender, @mentions and shared files. Supports a since/until window and nextCursor for older messages. Requires delegated Chat.Read. Chinese intents / 中文意图: 查看Teams聊天消息, 读取聊天记录, 查看群聊消息, 看某段时间的聊天.

Input Schema

NameRequiredDescriptionDefault
topNoMessages to fetch per page, from 1 to 50. Defaults to 20.
sinceNoOnly messages sent at or after this ISO date-time (China Standard Time if no offset).
untilNoOnly messages sent before this ISO date-time.
chatIdYesChat ID from teams_list_chats.
cursorNonextCursor from the previous call, with the same other arguments.
formatNoMessage body format. Defaults to text.
includeSystemMessagesNoInclude system events such as members added or meeting started. Defaults to false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.2.0
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "nextCursor from the previous call, with the same other arguments.",
+  "maxLength": 4000,
+  "type": "string"
+}
    • addedInput schema / properties / format
      Added value: +{
+  "description": "Message body format. Defaults to text.",
+  "enum": [
+    "text",
+    "html"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / includeSystemMessages
      Added value: +{
+  "description": "Include system events such as members added or meeting started. Defaults to false.",
+  "type": "boolean"
+}
    • addedInput schema / properties / since
      Added value: +{
+  "description": "Only messages sent at or after this ISO date-time (China Standard Time if no offset).",
+  "maxLength": 40,
+  "type": "string"
+}
    • changedInput schema / properties / top / description
      Previous value: -"Number of messages to return, from 1 to 50."New value: +"Messages to fetch per page, from 1 to 50. Defaults to 20."
    • addedInput schema / properties / until
      Added value: +{
+  "description": "Only messages sent before this ISO date-time.",
+  "maxLength": 40,
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real value beyond them: the per-page ordering, the auth requirement, the fact that system messages are excluded by default, and what each message contains. Return format and pagination interplay are not fully spelled out, keeping it below 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and scope in the first sentence, then pagination and auth. The Chinese intent list is useful for retrieval but adds length; overall still tight and free of filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter read tool with no output schema, the description covers ordering, page size default, content returned, paging via nextCursor, and the required permission. Auth and system-message defaults are highlighted, so an agent has enough to invoke it correctly, though it does not describe error or empty-result behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so top, since, until, cursor, format and includeSystemMessages are already documented in the schema. The description restates the since/until window and nextCursor without adding syntax or format detail beyond what the schema provides, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Read messages in a Teams chat') plus the returned shape (plain text, sender, @mentions, shared files) and ordering (oldest first within a page). This clearly distinguishes it from sibling list/search tools like mail_list_messages and teams_list_chats.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains the since/until window and that nextCursor pages to older messages, and names the required permission (delegated Chat.Read). It gives clear operational context but does not explicitly contrast itself with alternatives such as mail_search_messages for keyword lookups.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools