Skip to main content
Glama

update_room_tab

Modify a room tab in Webex by updating its content URL and display name, ensuring accurate and relevant information is displayed for users.

Instructions

Update a Room Tab in Webex.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentUrlYesThe new content URL for the tab.
displayNameYesThe display name for the tab.
idYesThe unique identifier for the Room Tab.
roomIdYesThe ID of the room to which the tab belongs.

Implementation Reference

  • The main handler function that executes the tool logic. It constructs the Webex API URL, prepares the request body with roomId, contentUrl, and displayName, sends a PUT request, and handles the response or errors.
    const executeFunction = async ({ id, roomId, contentUrl, displayName }) => {
    
      try {
        // Construct the URL with the path variable
        const url = getWebexUrl(`/room/tabs/${encodeURIComponent(id)}`);
    
        // Prepare the request body
        const body = JSON.stringify({
          roomId,
          contentUrl,
          displayName
        });
    
        // Set up headers for the request
        const headers = getWebexJsonHeaders();
    
        // Perform the fetch request
        const response = await fetch(url, {
          method: 'PUT',
          headers,
          body
        });
    
        // Check if the response was successful
        if (!response.ok) {
          const errorData = await response.json();
          throw new Error(errorData);
        }
    
        // Parse and return the response data
        const data = await response.json();
        return data;
      } catch (error) {
        console.error('Error updating Room Tab:', error);
        return { error: 'An error occurred while updating the Room Tab.' };
      }
    };
  • The JSON schema definition for the tool's input parameters, including types, descriptions, and required fields.
      name: 'update_room_tab',
      description: 'Update a Room Tab in Webex.',
      parameters: {
        type: 'object',
        properties: {
          id: {
            type: 'string',
            description: 'The unique identifier for the Room Tab.'
          },
          roomId: {
            type: 'string',
            description: 'The ID of the room to which the tab belongs.'
          },
          contentUrl: {
            type: 'string',
            description: 'The new content URL for the tab.'
          },
          displayName: {
            type: 'string',
            description: 'The display name for the tab.'
          }
        },
        required: ['id', 'roomId', 'contentUrl', 'displayName']
      }
    }
  • The apiTool export that registers the handler function with its schema definition for the MCP tool system.
    const apiTool = {
      function: executeFunction,
      definition: {
        type: 'function',
        function: {
          name: 'update_room_tab',
          description: 'Update a Room Tab in Webex.',
          parameters: {
            type: 'object',
            properties: {
              id: {
                type: 'string',
                description: 'The unique identifier for the Room Tab.'
              },
              roomId: {
                type: 'string',
                description: 'The ID of the room to which the tab belongs.'
              },
              contentUrl: {
                type: 'string',
                description: 'The new content URL for the tab.'
              },
              displayName: {
                type: 'string',
                description: 'The display name for the tab.'
              }
            },
            required: ['id', 'roomId', 'contentUrl', 'displayName']
          }
        }
      }
    };
    
    export { apiTool };
  • Imports helper functions from webex-config.js used for constructing API URLs and headers.
    import { getWebexUrl, getWebexHeaders, getWebexJsonHeaders } from '../../../lib/webex-config.js';
Behavior2/5

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

With no annotations provided, the description carries full burden but only states it's an update operation. It doesn't disclose behavioral traits like required permissions, whether it's idempotent, what happens to unspecified fields, error conditions, or rate limits. This is inadequate for a mutation tool with zero annotation coverage.

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, clear sentence with zero wasted words. It's appropriately sized and front-loaded with the essential information about what the tool does.

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 mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'update' entails behaviorally, what values can be changed, what the response looks like, or potential side effects. Given the complexity of updating a resource in a collaboration system, more context is needed.

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 input schema has 100% description coverage, so all parameters are documented in the schema itself. The description adds no additional parameter information beyond what's in the schema, which meets the baseline expectation when schema coverage is complete.

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 ('Update') and resource ('a Room Tab in Webex'), making the purpose immediately understandable. However, it doesn't distinguish this tool from sibling update tools like update_room or update_team, which follow the same pattern for different resources.

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 about when to use this tool versus alternatives. The description doesn't mention prerequisites (like needing an existing room tab ID), when not to use it, or how it differs from create_room_tab or delete_room_tab among the siblings.

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