Skip to main content
Glama

graph_list_channel_members

Lists members of a Microsoft Teams channel using a team ID and channel ID, with optional next-link paging to retrieve additional results.

Instructions

List members of a channel.

Args: team_id: The team ID (from graph_list_teams). channel_id: The channel ID (from graph_list_channels). 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>"
    },
    "name": "graph_list_channel_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
team_idYes
next_linkNo
channel_idYes
include_next_linkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A4/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 disclose real behavior: the default returns a bare list, include_next_link=true wraps it as {items, next_link}, and next_link overrides the other paging arguments when supplied. Missing are permission requirements and any indication of page-size or failure behavior, which keeps it from a 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?

The purpose line is front-loaded and wastes nothing, and the Args block is justified given 0% schema coverage. It is docstring-shaped rather than prose, so the purpose statement is very terse relative to the amount of parameter detail, but no sentence is 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 read-only list tool with no annotations and no output schema, the definition covers the two things an agent most needs: where the IDs come from and how paging/return shape works. It leaves member object contents and permission prerequisites unstated, but those are modest gaps for a straightforward listing call.

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

Parameters5/5

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

Schema description coverage is 0% and there are four parameters, yet the description documents all of them: it gives provenance for team_id and channel_id, states that next_link is an opaque URL from a prior call, and explains the default and precedence of include_next_link. That is exactly the compensation required when the schema is bare.

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 first line states a specific verb and resource ('List members of a channel'), and the Args section reinforces scope by tying team_id/channel_id to graph_list_teams and graph_list_channels. It stops short of distinguishing itself from graph_list_team_members or graph_list_chat_members, so an agent must infer that 'channel' means channel-scoped rather than team- or chat-scoped.

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 provenance notes tell the agent to call graph_list_teams and graph_list_channels first, which is genuine workflow guidance. There is no explicit when-to-use/when-not or any mention of the sibling member-listing tools that would make the choice unambiguous.

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