Skip to main content
Glama

get_message_details

Retrieve detailed information about a specific message in Webex using its unique ID. Enables precise message analysis and management within Cisco Webex messaging systems.

Instructions

Get details of a message by its ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageIdYesThe unique identifier for the message.

Implementation Reference

  • The core handler function `executeFunction` that implements the tool logic: fetches message details from Webex API using the `messageId`, handles HTTP errors, and returns the JSON response or an error object.
    const executeFunction = async ({ messageId }) => {
    
      try {
        // Construct the URL with the message ID
        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: 'GET',
          headers
        });
    
        // Check if the response was successful
        if (!response.ok) {
          const errorData = await response.json();
          throw new Error(JSON.stringify(errorData));
        }
    
        // Parse and return the response data
        const data = await response.json();
        return data;
      } catch (error) {
        console.error('Error fetching message details:', error);
        return {
          error: error.message || 'An error occurred while fetching message details.',
          details: error.stack
        };
      }
    };
  • The input parameters schema specifying a required `messageId` string for the tool.
    parameters: {
      type: 'object',
      properties: {
        messageId: {
          type: 'string',
          description: 'The unique identifier for the message.'
        }
      },
      required: ['messageId']
    }
  • lib/tools.js:7-16 (registration)
    Central registration/discovery function that dynamically imports all Webex tool modules (including get-message-details.js) via paths.js and spreads their `apiTool` definitions to register them as MCP tools.
    export async function discoverTools() {
      const toolPromises = toolPaths.map(async (file) => {
        const module = await import(`../tools/${file}`);
        return {
          ...module.apiTool,
          path: file,
        };
      });
      return Promise.all(toolPromises);
    }
  • tools/paths.js:16-16 (registration)
    The path to the get_message_details tool file, listed for use in dynamic tool discovery and registration.
    'webex-public-workspace/webex-messaging/get-message-details.js',
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Get details' but doesn't clarify if this is a read-only operation, what permissions are needed, the format of returned details, or any rate limits. For a tool with no annotation coverage, this leaves significant behavioral gaps.

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, front-loaded sentence with zero waste: 'Get details of a message by its ID.' It efficiently conveys the core purpose without unnecessary elaboration, making it highly concise and well-structured.

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?

Given the lack of annotations and output schema, the description is incomplete. It doesn't address behavioral aspects like safety, permissions, or return format, which are crucial for a tool that retrieves data. While concise, it fails to provide enough context for an agent to use it confidently without additional inference.

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?

The description adds no parameter semantics beyond the input schema, which has 100% coverage for the single parameter 'messageId'. Since the schema already fully describes the parameter, the baseline score of 3 is appropriate—the description doesn't compensate but doesn't need to given the 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 verb ('Get details') and resource ('of a message'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_message_details' vs 'get_event_details' or 'list_messages', which share similar 'get' patterns but target different resources or scopes.

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?

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'list_messages' (for listing) and 'get_event_details' (for other resource types), there's no indication of context, prerequisites, or exclusions, leaving the agent to infer usage based on naming alone.

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