Local MCP

Teams Read Channel Messages

teams_read_channel_messages

Read-only

Reads the most recent posts of a Microsoft Teams channel (team_id from teams_list_teams, channel_id from teams_list_channels), oldest first, from Microsoft 365. Top-level posts only: replies are not included. Reading channel messages needs a permission that an administrator of the Microsoft 365 organization approves; without it the answer is consent_required and says what to do. Reads at most 20 pages of 50 posts, deleted ones included. When the read is cut (by that bound, or because the call ran out of time) the answer has truncated: true. Needs a work or school Microsoft 365 account connected with connect_m365_account (personal Microsoft accounts have no Teams reads).

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max items to return (default 50)
`account`	No	Which connected Microsoft 365 account to use: its email (UPN), its id from list_m365_accounts, or its display name when unique. Leave it out to use the default account.
`team_id`	Yes	Team ID from teams_list_teams
`channel_id`	Yes	Channel ID from teams_list_channels

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No
`count`	No
`error`	No
`account`	No	The email (UPN) of the Microsoft 365 account this call used.
`messages`	No
`truncated`	No	Present and true only when the read was cut before it had everything it was asked for.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 5, 2026

addedInput schema / properties / account

Added value: +{
+  "description": "Which connected Microsoft 365 account to use: its email (UPN), its id from list_m365_accounts, or its display name when unique. Leave it out to use the default account.",
+  "type": "string"
+}

changedInput schema / properties / limit / description

Previous value: -"Max messages (default 50)"New value: +"Max items to return (default 50)"

changedInput schema / properties / team_id / description

Previous value: -"Team ID"New value: +"Team ID from teams_list_teams"

addedOutput schema / properties / account

Added value: +{
+  "description": "The email (UPN) of the Microsoft 365 account this call used.",
+  "type": "string"
+}

addedOutput schema / properties / note
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / truncated

Added value: +{
+  "description": "Present and true only when the read was cut before it had everything it was asked for.",
+  "type": "boolean"
+}

Changed1 schema field changedJul 30, 2026

changedInput schema / properties / channel_id / description

Previous value: -"Channel ID from list_teams_channels"New value: +"Channel ID from teams_list_channels"

First observedJun 30, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the readOnly/openWorld annotations by disclosing the admin-approved permission gate and the exact failure mode (consent_required), the pagination bound (20 pages of 50 posts), the inclusion of deleted posts, and the truncated: true signal. These are operational traits an agent could not infer from annotations or schema.

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-loads what the tool returns and its scope, then layers constraints, errors, and pagination. It is dense with little waste, though several clauses (deleted posts, truncation bound) could be tightened.

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?

An output schema exists, so return-value documentation is unnecessary; combined with the permission, account-type, pagination, and truncation disclosures, an agent has everything needed to call it correctly and interpret failure modes.

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 every parameter including account and limit is already documented in the schema; the description only restates that team_id and channel_id come from the list siblings. Baseline 3 applies since the schema carries the parameter semantics.

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 ('Reads the most recent posts of a Microsoft Teams channel') and scopes it precisely (recent posts, oldest first, top-level only), which separates it from teams_read_chat_messages and teams_search_messages.

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?

Gives prerequisites and routing for its inputs (team_id from teams_list_teams, channel_id from teams_list_channels) and states the admin-consent requirement plus the work/school account constraint. It does not explicitly compare itself to sibling readers like teams_read_chat_messages or teams_search_messages, so it stops short of full when/when-not guidance.

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

All Local MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.