Skip to main content
Glama

create_room_tab

Add a customizable tab to a Webex room by specifying the room ID, tab URL, and display name for enhanced collaboration and resource access.

Instructions

Create a tab in a specified room.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentUrlYesThe URL to be displayed in the tab.
displayNameYesThe name to be displayed for the tab.
roomIdYesThe ID of the room where the tab will be added.

Implementation Reference

  • The main handler function that executes the tool logic: constructs Webex API URL, sets headers, sends POST request with roomId, contentUrl, displayName to create a room tab, handles errors.
    const executeFunction = async ({ roomId, contentUrl, displayName }) => {
    
      try {
        // Construct the URL for the request
        const url = getWebexUrl('/room/tabs');
    
        // Set up headers for the request
        const headers = getWebexJsonHeaders();
    
        // Prepare the body of the request
        const body = JSON.stringify({
          roomId,
          contentUrl,
          displayName
        });
    
        // Perform the fetch request
        const response = await fetch(url, {
          method: 'POST',
          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 creating room tab:', error);
        return { error: 'An error occurred while creating the room tab.' };
      }
    };
  • Input schema definition for the create_room_tab tool, specifying parameters roomId, contentUrl, displayName as required strings.
      type: 'function',
      function: {
        name: 'create_room_tab',
        description: 'Create a tab in a specified room.',
        parameters: {
          type: 'object',
          properties: {
            roomId: {
              type: 'string',
              description: 'The ID of the room where the tab will be added.'
            },
            contentUrl: {
              type: 'string',
              description: 'The URL to be displayed in the tab.'
            },
            displayName: {
              type: 'string',
              description: 'The name to be displayed for the tab.'
            }
          },
          required: ['roomId', 'contentUrl', 'displayName']
        }
      }
    }
  • The apiTool object that registers the tool by associating the executeFunction handler with the schema definition under the name 'create_room_tab' and exports it.
    const apiTool = {
      function: executeFunction,
      definition: {
        type: 'function',
        function: {
          name: 'create_room_tab',
          description: 'Create a tab in a specified room.',
          parameters: {
            type: 'object',
            properties: {
              roomId: {
                type: 'string',
                description: 'The ID of the room where the tab will be added.'
              },
              contentUrl: {
                type: 'string',
                description: 'The URL to be displayed in the tab.'
              },
              displayName: {
                type: 'string',
                description: 'The name to be displayed for the tab.'
              }
            },
            required: ['roomId', 'contentUrl', 'displayName']
          }
        }
      }
    };
    
    export { apiTool };
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 'Create' which implies a write/mutation operation, but doesn't disclose any behavioral traits: no information about permissions required, whether the operation is idempotent, rate limits, what happens on failure, or what the response looks like. For a mutation tool with zero annotation coverage, this is a significant gap.

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 front-loaded with the core action and immediately specifies the context. Every word earns its place, making it highly efficient for an agent to parse.

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 this is a mutation tool (create operation) with no annotations and no output schema, the description is incomplete. It doesn't explain what a successful creation returns, error conditions, or behavioral constraints. The agent lacks crucial information needed to properly invoke and handle responses from this tool.

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 schema description coverage is 100%, with all three parameters well-documented in the schema itself. The description adds no additional parameter information beyond what's already in the schema (roomId, contentUrl, displayName). According to the scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 ('Create a tab') and the target resource ('in a specified room'), making the purpose immediately understandable. It distinguishes from siblings like 'create_room' or 'create_message' by specifying the tab creation context. However, it doesn't explicitly differentiate from 'update_room_tab' or explain what a 'tab' represents in this system.

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. It doesn't mention prerequisites (e.g., needing an existing room), when not to use it, or how it differs from similar tools like 'update_room_tab' or 'create_attachment_action'. The agent must infer usage from the name and context 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