webex-mcp

Overview Schema Source Related Servers Discussions Admin

webex_create_space

Creates a Webex space with a required title and optional team, visibility, lock, and announcement settings for organizing team communication.

Instructions

Create a space.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "<title>"
    },
    "name": "webex_create_space"
  }
}

Input Schema

Name	Required	Description
`title`	Yes	Title
`teamId`	No	Team ID
`isLocked`	No	Locked
`isPublic`	No	Public to org
`description`	No	Description
`isAnnouncementOnly`	No	Moderators only

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Nov 7, 2026

TDQS

C2.5/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and fails to meet it. It does not state that authentication/authorship is required, what defaults apply to isLocked or isPublic when omitted, whether the creator becomes a member or moderator, or that the created space's identifier is returned for follow-up calls.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of waste, but it is undersized rather than appropriately concise. For a six-parameter mutation tool with no annotations, this brevity reflects under-specification rather than efficiency.

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?

The tool is a mutation with no annotations and no output schema, so the description should explain prerequisites, default behavior, and the resulting object. It does none of these, leaving an agent with only the bare operation name relative to the tool's complexity.

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%, so the schema already documents all six parameters, and the baseline of 3 applies. The description adds no extra meaning about accepted title formats, team-versus-standalone space behavior, or what isAnnouncementOnly implies for membership.

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

Purpose3/5

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

"Create a space" gives a clear verb and resource, so an agent knows the basic operation. But it merely restates the tool name and offers no differentiation from siblings such as webex_create_team or webex_create_message, which are also creation tools in this family.

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?

There is no guidance on when to use this tool, no prerequisites, and no mention of alternatives. An agent must infer from the name alone that this is the entry point for provisioning a new space rather than adding to an existing one.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server