Skip to main content
Glama

graph_create_channel

Create a standard, private, or shared channel in a Microsoft Teams team to organize conversations and collaboration by topic or project.

Instructions

Create a channel in a team.

Needs the Channel.Create permission.

Args: team_id: The team ID (from graph_list_teams). display_name: Name of the new channel. description: Optional channel description. membership_type: Channel type: "standard", "private", or "shared" (default "standard").

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>",
      "display_name": "<display_name>"
    },
    "name": "graph_create_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
team_idYes
descriptionNo
display_nameYes
membership_typeNostandard

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden; it usefully discloses the Channel.Create permission requirement, which is genuine added value. It does not say whether creation is reversible, what happens on a duplicate display_name, whether 'private'/'shared' need owner or member setup, or what the call returns, leaving the mutation's side effects under-described.

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 action statement is front-loaded, followed by the permission prerequisite, then a compact Args list — a predictable, scannable structure. The Args block is somewhat redundant with the schema field names, but with 0% schema coverage that restatement earns its place.

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 four-parameter mutation with no annotations and no output schema, the description covers purpose, permission, and every parameter, which is broadly adequate. It is incomplete on result format and on side effects such as duplicate-name handling or membership implications for non-standard channel types.

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 four parameters are named, team_id's provenance is given, description is flagged as optional, and membership_type is explained as the channel type with its three allowed values and the 'standard' default. The only shortfall is that it does not explain how 'private' or 'shared' differ behaviorally.

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 opens with 'Create a channel in a team,' a specific verb plus resource with scope ('in a team') that separates it from chat-creation siblings like graph_create_chat. It does not explicitly state why a channel must be created inside a team rather than a standalone chat, so sibling differentiation is implied rather than spelled out.

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

Usage Guidelines4/5

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

It states the required prerequisite ('Needs the Channel.Create permission') and points to graph_list_teams as the source for team_id, giving an agent clear context for invoking it correctly. It stops short of explicit when-not guidance or naming an alternative tool for chat creation, so it is context-rich but not exhaustively bounded.

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