Skip to main content
Glama

graph_update_channel_message

Edit a Microsoft Teams channel message you posted by team, channel, and message ID, replacing its content with HTML or plain text. Only your own messages can be updated.

Instructions

Edit a channel message you posted.

Only your own messages can be edited; editing anyone else's message fails.

Args: team_id: The team ID (from graph_list_teams). channel_id: The channel ID (from graph_list_channels). message_id: The message ID to edit (from graph_get_channel_messages). message: Replacement message content. When is_html is true, send explicit HTML; markdown is not converted. is_html: Whether the message is HTML content (default: True). Use false for plain text.

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>",
      "message": "<message>"
    },
    "name": "graph_update_channel_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
is_htmlNo
messageYes
team_idYes
channel_idYes
message_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.8/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 disclosure burden. It does reveal the ownership constraint and the failure mode for other users' messages, plus the notable is_html rule that markdown is not converted, but it never says that the edit replaces the message body entirely, what permissions/scopes are required, or what the tool returns on success.

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 two-sentence lead with the ownership constraint is front-loaded, and the Args block is compact and scannable. The Args list partially restates the schema's parameter names, but each entry adds provenance or behavior, so little is wasted.

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 five-parameter mutation tool with no annotations and no output schema, the definition covers the parameters, the permission boundary, and a format gotcha. The remaining gap is the response/return behavior and error shape, which is minor but not fully covered.

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 supply all parameter meaning, and it does document every one of the five: identifier provenance for team_id, channel_id, and message_id, plus the replacement semantics of message and the is_html default of true with the no-markdown-conversion caveat. It adds genuine meaning beyond the bare types.

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 a specific verb and resource: "Edit a channel message you posted." The word "channel" implicitly separates it from chat-message siblings such as graph_update_chat_message, but no sibling is named explicitly, so an agent must infer that distinction from the resource noun alone.

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 a clear precondition ("Only your own messages can be edited; editing anyone else's message fails"), which tells the agent when this call will succeed. It also points to the source tools for each identifier (graph_list_teams, graph_list_channels, graph_get_channel_messages), which gives workflow context even though no alternative tool is named for the wrong-context case.

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