Skip to main content
Glama

Read Teams Channel Messages

list_channel_messages
Read-only

Retrieve recent messages from a Microsoft Teams channel to review conversations, with options to limit the number of results or fetch all pages.

Instructions

List recent messages in a channel

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": {
      "team_id": "<team_id>",
      "channel_id": "<channel_id>"
    },
    "name": "list_channel_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoNumber of messages (default: 25)
team_idYesTeam ID
channel_idYesChannel ID
fetch_all_pagesNoFetch all pages of results (max 50 pages)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

readOnlyHint=true already covers the safety profile, so the description would need to add context such as ordering, what "recent" means, pagination behavior, or rate limits. It adds none of that, and it does not reconcile "recent" with the fetch_all_pages parameter, which implies unbounded retrieval.

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?

A single short sentence, front-loaded with the verb and resource, with no filler. It is efficient, though the brevity comes at the cost of specification rather than from tight editing of richer content.

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

Completeness2/5

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

For a four-parameter tool with pagination (fetch_all_pages, max 50 pages) and no output schema, the description says nothing about return shape, ordering, or page limits. An agent calling it correctly needs more than the one sentence provides.

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 the schema already documents top, team_id, channel_id, and fetch_all_pages. The description contributes nothing about parameter meaning or defaults beyond the word "recent", so the baseline of 3 applies.

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

Purpose3/5

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

The description gives a verb and resource ("List recent messages in a channel"), which is better than a tautology, but "recent" is undefined and nothing distinguishes it from siblings such as list_chat_messages or list_messages. An agent cannot tell from the description alone which message-listing tool applies to which surface.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of prerequisites (team_id and channel_id must already be known), and no pointer to alternatives for chat or general messages. The agent must infer usage entirely from the name.

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