Skip to main content
Glama

delete_webex_room

Remove a Webex room permanently by providing its room ID. The room and all its content are deleted from the workspace.

Instructions

Delete a Webex room.

Args: room_id: Room ID to delete (required)

Returns: Standardized response dictionary with success/error information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
room_idYes
Behavior2/5

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

No annotations, and the description only says 'Delete'. No details on permanence, required permissions, cascading effects on messages or memberships, or error cases. Minimal behavioral disclosure.

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?

Extremely concise: two sentences plus a parameter list. Every piece of information serves a purpose with no fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a simple delete operation with one parameter and no output schema. Covers purpose, parameter, return type. Lacks behavioral details (e.g., permanence, side effects) which are important for a destructive tool, but overall functional.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% (no description in schema). The description adds 'Room ID to delete (required)', clarifying the parameter's nature. While concise, it provides essential context beyond the schema's title. Could include format or source hints.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states 'Delete a Webex room', using a specific verb and resource. The sibling tools delete different resources (membership, message, space, team), making this tool's purpose distinct and unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies usage for deleting a room but provides no explicit when-to-use or when-not-to-use guidance. No alternative tools mentioned, though sibling names make it inferable.

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

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/WebexCommunity/webex-bot-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server