Skip to main content
Glama
Sign In
webex-mcp

webex-mcp

by yuryev89
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

webex_delete_message

Delete a Webex message by its ID to remove content from a space or conversation.

Instructions

Delete a message by ID.

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": {
      "messageId": "<messageId>"
    },
    "name": "webex_delete_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageIdYesMessage ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden for a destructive mutation. It implies removal via 'Delete' but says nothing about irreversibility, required permissions, whether the message is removed for all participants, or how failure (unknown/inaccessible ID) is reported. The word 'delete' alone is the only behavioral signal.

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?

One short sentence with the action and key front-loaded and zero filler. It is appropriately sized but borders on terse given the tool performs an irreversible operation.

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

Completeness2/5

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

For a destructive operation with no annotations and no output schema, the definition leaves out authorization requirements, irreversibility, and observable return/error behavior. The simple one-parameter schema limits the damage, but an agent has no basis to decide whether calling this is safe.

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 a single required parameter, so the schema already defines messageId as a string. The description adds nothing beyond echoing that the ID identifies the message, which is the expected baseline when the schema does the work.

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 uses a specific verb ('Delete') on a specific resource ('a message'), plus the lookup key ('by ID'). Siblings contain other delete tools (webex_delete_space, webex_delete_team, webex_delete_webhook) but the resource noun disambiguates them cleanly. It stops short of stating scope (e.g., whether the caller must be the author) but purpose is unmistakable.

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 versus webex_update_message or webex_save_message_files, and no prerequisites such as needing to be the message author or a space moderator. An agent must guess at the conditions under which deletion will succeed.

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