Skip to main content
Glama

delete_message

Delete specific messages in Webex using the message ID, ensuring precise content removal through the Webex MCP Server.

Instructions

Delete a message in Webex by message ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageIdYesThe unique identifier for the message to be deleted.

Implementation Reference

  • The main handler function that executes the deletion of a Webex message by making a DELETE request to the `/messages/{messageId}` endpoint using Webex configuration utilities.
    const executeFunction = async ({ messageId }) => {
    
      try {
        // Construct the URL for the delete request
        const url = getWebexUrl(`/messages/${encodeURIComponent(messageId)}`);
    
        // Set up headers for the request
        const headers = getWebexHeaders();
    
        // Perform the fetch request
        const response = await fetch(url, {
          method: 'DELETE',
          headers
        });
    
        // Check if the response was successful
        if (!response.ok) {
          const errorData = await response.json();
          throw new Error(JSON.stringify(errorData));
        }
    
        // Return the response status
        return { status: response.status, message: 'Message deleted successfully.' };
      } catch (error) {
        console.error('Error deleting message:', error);
        return {
          error: error.message || 'An error occurred while deleting the message.',
          details: error.stack
        };
      }
    };
  • The apiTool export that registers the 'delete_message' tool, linking the handler function to its schema definition for MCP integration.
    const apiTool = {
      function: executeFunction,
      definition: {
        type: 'function',
        function: {
          name: 'delete_message',
          description: 'Delete a message in Webex by message ID.',
          parameters: {
            type: 'object',
            properties: {
              messageId: {
                type: 'string',
                description: 'The unique identifier for the message to be deleted.'
              }
            },
            required: ['messageId']
          }
        }
      }
    };
  • JSON schema defining the input parameters for the delete_message tool: an object requiring 'messageId' as a string.
    parameters: {
      type: 'object',
      properties: {
        messageId: {
          type: 'string',
          description: 'The unique identifier for the message to be deleted.'
        }
      },
      required: ['messageId']
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool deletes a message but doesn't mention critical aspects like whether deletion is permanent, requires specific permissions, has rate limits, or what happens on success/failure. This is a significant gap for a destructive operation.

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

Conciseness5/5

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

The description is a single, efficient sentence with zero wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly.

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 tool with no annotations and no output schema, the description is incomplete. It lacks behavioral details (e.g., permanence, permissions), usage context, and error handling information, leaving the agent with insufficient guidance for safe invocation.

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%, so the schema already documents the 'messageId' parameter fully. The description adds no additional meaning beyond what's in the schema, such as format examples or constraints, meeting the baseline for high schema coverage.

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 clearly states the action ('Delete') and resource ('a message in Webex by message ID'), making the purpose immediately understandable. It doesn't explicitly distinguish from siblings like 'delete_membership' or 'delete_room', but the specificity of 'message' provides adequate differentiation.

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?

No guidance is provided on when to use this tool versus alternatives like 'edit_message' or other deletion tools. The description lacks context about prerequisites (e.g., permissions needed) or constraints (e.g., only messages you own can be deleted).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Kashyap-AI-ML-Solutions/webex-messaging-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server