Skip to main content
Glama

List Teams Channels

list_channels
Read-only

Lists channels in a Microsoft Teams team by team ID, with optional pagination to fetch all available result pages.

Instructions

List channels in a team

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": "list_channels"
  }
}

Input Schema

NameRequiredDescriptionDefault
team_idYesTeam 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.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered by structured data. Beyond that the description adds nothing: no mention of pagination behavior, the 50-page cap implied by fetch_all_pages, ordering, or result size, all of which matter for a paginated list tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Five words, front-loaded, with zero filler. However, the brevity crosses into under-specification for a tool with a pagination flag, so it is efficient but not proportionate.

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

Completeness3/5

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

For a simple read-only list tool with a fully documented two-parameter schema and no output schema, the description is adequate to call correctly. It leaves out pagination semantics and the relationship to the parent list_teams tool, which an agent would benefit from knowing.

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%, with both team_id and fetch_all_pages documented in the schema, so the baseline of 3 applies. The description adds no meaning beyond the schema, not even noting that team_id must come from list_teams.

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 description states a specific verb and resource ("List channels") scoped to a team, which is clear enough to act on. It does not distinguish itself from siblings such as list_channel_messages or list_teams, so an agent must rely on the name alone to pick the right list tool.

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 guidance on when to use this instead of list_channel_messages or list_teams, and no mention of prerequisites such as needing a valid team_id. The single phrase implies usage at best.

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