Skip to main content
Glama

Read Teams Chat Messages

list_chat_messages
Read-only

Retrieve messages from a Microsoft Teams chat, newest first, with sender, timestamp, flags, and filters for time and count. Use it to review recent activity or catch edits.

Instructions

List messages in a Teams chat, newest first. Each message is a line '- () [You] [App] [Urgent|High importance] [Mentions you] (ID: )' (flags only when they apply), followed by its text on a ' > ' line. System events (joins, renames) and deleted messages are left out.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "chat_id": "<chat_id>"
    },
    "name": "list_chat_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoNumber of messages (default: 25, max 50)
sinceNoOnly messages created or changed after this ISO 8601 time with a time zone, e.g. 2026-10-01T00:00:00Z. An old message edited after it is included; its line still shows when it was created. Returns at most top messages (default 25); if more match, the output ends with 'Note: more messages match; raise top or move since later to see them.'
chat_idYesChat ID
max_charsNoCut each message's text at this length (default: 300)
fetch_all_pagesNoFetch all pages of results (max 50 pages)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, so safety needs no restating. The description adds real behavioral context the annotations do not cover: descending order, the exact per-message line layout with conditional flags, and, importantly, that system events (joins, renames) and deleted messages are excluded — telling the agent its result set is filtered. It stops short of mentioning truncation or the 'more messages match' note, though both appear in the schema.

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

Conciseness5/5

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

Two sentences, no filler: the ordering and scope come first, then the output contract, then the exclusions. The embedded format template is compact and directly useful for parsing results.

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

Completeness5/5

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

With five parameters but full schema coverage and no output schema, the only real gap would be the result format — and the description specifies it precisely, including ordering and filtering. Nothing an agent needs to call or interpret this tool is missing.

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%, with top, since, max_chars, and fetch_all_pages each documented in detail including defaults, bounds, and edge cases like edited messages. The description adds no parameter-level meaning beyond implying that text is rendered under a ' > ' line, so the baseline of 3 applies.

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

Purpose4/5

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

The description gives a specific verb and resource ('List messages in a Teams chat') plus an ordering guarantee ('newest first'), and the required chat_id bounds the operation to a specific chat. It does not explicitly contrast itself with the similar-looking siblings list_channel_messages or list_messages, so an agent must infer the chat-vs-channel distinction from the parameter name alone.

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

Usage Guidelines3/5

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

Usage is implied by the tool's shape — read the history of an existing chat — but there is no explicit when-to-use or when-not-to-use statement, and no alternative tool is named for cases like searching or reading channel posts. The guidance is adequate but leaves routing to the agent's inference.

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