Skip to main content
Glama

delete_team

Remove a team from Webex by specifying its unique ID to manage and organize workspace structures effectively.

Instructions

Delete a team by ID in Webex.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
teamIdYesThe unique identifier for the team to be deleted.

Implementation Reference

  • The main handler function 'executeFunction' that performs the logic to delete a team by ID using a DELETE request to the Webex API.
    const executeFunction = async ({ teamId }) => {
    
      try {
        // Construct the URL with the team ID
        const url = getWebexUrl(`/teams/${encodeURIComponent(teamId)}`);
    
        // 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);
        }
    
        // Return the response status
        return { status: response.status, message: 'Team deleted successfully.' };
      } catch (error) {
        console.error('Error deleting team:', error);
        return { error: 'An error occurred while deleting the team.' };
      }
    };
  • The tool definition object 'apiTool' that includes the schema for the 'delete_team' tool, specifying parameters and description.
    const apiTool = {
      function: executeFunction,
      definition: {
        type: 'function',
        function: {
          name: 'delete_team',
          description: 'Delete a team by ID in Webex.',
          parameters: {
            type: 'object',
            properties: {
              teamId: {
                type: 'string',
                description: 'The unique identifier for the team to be deleted.'
              }
            },
            required: ['teamId']
          }
        }
      }
    };
Behavior2/5

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

No annotations are provided, so the description carries full burden. 'Delete' implies a destructive mutation, but the description doesn't disclose critical behavioral traits like whether deletion is permanent, what permissions are required, what happens to associated resources (memberships, rooms), or error conditions.

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 immediately understandable without unnecessary elaboration.

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 inadequate. It doesn't explain what 'delete' entails behaviorally, what the response looks like, or any side effects—critical gaps given the tool's complexity and potential impact.

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 'teamId' well-documented in the schema. The description adds no additional parameter information beyond what's already in the structured schema, meeting the baseline for high 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 team by ID in Webex'), making the purpose unambiguous. However, it doesn't differentiate this tool from other deletion tools like delete_membership or delete_room, which would be needed for a perfect score.

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 many sibling tools including other deletions and updates, there's no indication of prerequisites, consequences, or appropriate contexts for team deletion.

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