Skip to main content
Glama

graph_delete_channel_message

Soft-delete a Microsoft Teams channel message by team, channel, and message ID, or restore a previously deleted message when needed.

Instructions

Soft-delete a channel message, or restore one you deleted.

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 delete (from graph_get_channel_messages). restore: Whether to restore a previously soft-deleted message (default false).

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

Input Schema

NameRequiredDescriptionDefault
restoreNo
team_idYes
channel_idYes
message_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does contribute the key behavioral fact that deletion is soft and reversible via the restore flag. It omits whether permissions are required, whether the operation is idempotent, whether message content is retained, and what the call returns.

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 core operation and its inverse are front-loaded in a single sentence, followed by a compact Args block. The Google-style parameter section is slightly verbose for a four-field schema but every line carries information.

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?

There are no annotations and no output schema, so the description is the only source of behavioral context, and it covers the soft-delete/restore semantics but not return values, failure modes, or permission requirements. Adequate to invoke correctly, incomplete for predicting outcomes.

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: each of team_id, channel_id, and message_id is annotated with the sibling tool that supplies it, and restore is explained with its default. It does not clarify what happens when restore=true is passed on a message that was never deleted.

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 sentence names a specific verb and resource ("Soft-delete a channel message") plus the inverse operation (restore), so the agent knows exactly what the tool mutates. It does not explicitly contrast itself with the sibling graph_delete_chat_message, so differentiation is left implicit.

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 by the wording: this is the channel-message variant, while graph_delete_chat_message presumably covers chats. However, there is no explicit when-to-use/when-not-to-use statement, no note that the caller should prefer update_channel_message for edits, and no mention of prerequisites.

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