Skip to main content
Glama

graph_get_channel_message_replies

Retrieve replies to a Microsoft Teams channel message, with optional compact fields and pagination for paging through large reply threads.

Instructions

Get replies to a channel message.

Messages carry full HTML bodies plus their attachments and mentions, so compact narrows them to the identifying fields. Without it no $select is sent and the response is unchanged.

Args: team_id: The team ID (from graph_list_teams). channel_id: The channel ID (from graph_list_channels). message_id: The message ID whose replies to return. top: Maximum number of replies to return (default 50, maximum 50). compact: Whether to return only the identifying fields instead of the full record (default false). Use it to page through large collections cheaply. next_link: Opaque nextLink URL from a previous call, used to fetch the next page. Overrides the other paging arguments when supplied. include_next_link: Whether to wrap the result as {items, next_link} so paging can continue (default false, which returns a bare list).

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>",
      "message_id": "<message_id>"
    },
    "name": "graph_get_channel_message_replies"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo
compactNo
team_idYes
next_linkNo
channel_idYes
message_idYes
include_next_linkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses that replies contain full HTML bodies plus attachments and mentions, that omitting `compact` means no `$select` is sent, and that `include_next_link` changes the return shape to {items, next_link}. It omits permission/auth requirements and ordering guarantees, which is the remaining gap.

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?

The purpose is front-loaded, followed by a short behavioral paragraph and a per-argument list; every item earns its place. The Args block is somewhat verbose for parameters whose names are largely self-explanatory, but no sentence is pure 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 annotations and no output schema, the definition covers the response shape, paging mechanics, and per-parameter meaning well. It lacks any note on permissions or error conditions, and the `top` maximum conflict leaves a small ambiguity an agent might hit in practice.

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

Parameters4/5

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

Schema description coverage is 0%, so the Args block is the only documentation and it covers all seven parameters, including provenance hints (team_id from graph_list_teams, channel_id from graph_list_channels) and override semantics for next_link. One inconsistency lowers the score: the description claims `top` has a maximum of 50, while the schema declares a far larger maximum, which could confuse an agent reasoning about limits.

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 opening sentence names a specific verb and resource ("Get replies to a channel message"), which clearly separates it from graph_get_channel_messages (top-level messages) and graph_reply_to_channel_message (a write). It stops short of explicitly naming those siblings, so an agent must infer the distinction from the 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 rather than stated: the description explains that `compact` is for paging cheaply and that `next_link` overrides other paging arguments, which tells the agent how to iterate but not when to choose this tool over graph_get_channel_messages. There are no explicit when-not conditions or named alternatives.

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