Skip to main content
Glama

delete_room_tab

Remove a Room Tab in Webex by specifying its unique identifier, simplifying workspace management and ensuring clutter-free collaboration environments.

Instructions

Delete a Room Tab in Webex.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe unique identifier for the Room Tab to delete.

Implementation Reference

  • The handler function that executes the tool logic: constructs Webex API URL for /room/tabs/{id}, sends DELETE request with auth headers, handles response or error.
    const executeFunction = async ({ id }) => {
    
      try {
        // Construct the URL with the path variable
        const url = getWebexUrl(`/room/tabs/${encodeURIComponent(id)}`);
    
        // 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(errorData);
        }
    
        // Parse and return the response data
        return await response.json();
      } catch (error) {
        console.error('Error deleting Room Tab:', error);
        return { error: 'An error occurred while deleting the Room Tab.' };
      }
    };
  • Input schema definition: object with required 'id' property (string, unique identifier of the room tab).
    parameters: {
      type: 'object',
      properties: {
        id: {
          type: 'string',
          description: 'The unique identifier for the Room Tab to delete.'
        }
      },
      required: ['id']
    }
  • The apiTool export that defines the tool's name 'delete_room_tab', schema, description, and references the handler; discovered and registered via lib/tools.js.
    const apiTool = {
      function: executeFunction,
      definition: {
        type: 'function',
        function: {
          name: 'delete_room_tab',
          description: 'Delete a Room Tab in Webex.',
          parameters: {
            type: 'object',
            properties: {
              id: {
                type: 'string',
                description: 'The unique identifier for the Room Tab to delete.'
              }
            },
            required: ['id']
          }
        }
      }
    };
  • tools/paths.js:7-7 (registration)
    Specific path to this tool file listed in the toolPaths array used by discoverTools() for dynamic import.
    'webex-public-workspace/webex-messaging/delete-a-room-tab.js',
  • lib/tools.js:7-16 (registration)
    Generic tool discovery function that imports each tool file from paths.js and extracts the apiTool object for registration in MCP server.
    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);
    }
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. While 'Delete' clearly indicates a destructive operation, the description doesn't mention whether this requires specific permissions, whether the deletion is permanent or reversible, what happens to associated data, or any rate limits. For a destructive operation with zero annotation coverage, this represents a significant gap in behavioral transparency.

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 that communicates the essential purpose without unnecessary words. It's appropriately sized for a simple deletion operation and front-loads the key information. Every word earns its place in this concise formulation.

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 description is insufficiently complete. It doesn't address critical context like what constitutes a valid 'Room Tab' ID, whether the operation is idempotent, what confirmation (if any) is provided, or what happens on success/failure. The combination of a mutation tool with zero structured metadata requires more comprehensive description.

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 the single parameter 'id' clearly documented in the schema as 'The unique identifier for the Room Tab to delete.' The description doesn't add any additional parameter information beyond what's already in the schema. Since the schema does the heavy lifting, the baseline score of 3 is appropriate.

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 target resource ('a Room Tab in Webex'), making the purpose immediately understandable. It doesn't distinguish from sibling tools like 'delete_room' or 'delete_team', but the specificity of 'Room Tab' provides adequate differentiation. This is not a tautology and provides meaningful context about what will be deleted.

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. There are multiple deletion tools in the sibling list (delete_membership, delete_message, delete_room, etc.), but the description doesn't help an agent understand when to delete a Room Tab specifically versus other resources. No prerequisites, constraints, or alternative approaches are mentioned.

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