Skip to main content
Glama

graph_list_channels

List channels in a Microsoft Teams team by team ID, with optional paging to fetch additional pages of results.

Instructions

List channels in a team.

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

Input Schema

NameRequiredDescriptionDefault
team_idYes
next_linkNo
include_next_linkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose key behavior: include_next_link=false returns a bare list, true wraps results as {items, next_link}, and next_link overrides other paging arguments. It says nothing about permissions required, error conditions, or what a channel record contains, so disclosure is partial.

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 sentence is front-loaded and the remaining text is a tight per-argument list with no filler. Slight redundancy exists where defaults (false, empty string) are restated from the schema, but the behavioral explanation attached to include_next_link justifies the repetition.

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 three-parameter read-only list tool with no output schema, the definition covers inputs and paging semantics adequately. The main gap is that it never characterizes the returned channel data, which the absence of an output schema would otherwise make the description's responsibility.

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 description must compensate, and it does: all three parameters are explained, including the provenance of team_id, the opaque nature of next_link, the override precedence, and the concrete return-shape effect of include_next_link. Only the format/shape of the channel objects themselves is left unaddressed.

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 line gives a specific verb and resource, "List channels in a team," which is unambiguous. It does not explicitly differentiate itself from nearby siblings such as graph_list_channel_members, but it does route the agent to graph_list_teams as the source of team_id, which is useful orientation.

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 agent learns it needs a team_id from graph_list_teams, and that next_link exists for continuation, but there is no explicit when-to-use/when-not or comparison against alternatives. Paging guidance is the only conditional advice given.

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