Skip to main content
Glama
Sign In
webex-mcp

webex-mcp

by yuryev89
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

webex_create_team

Creates a Webex team by specifying its name and optional description, letting you organize people and spaces under a shared team structure.

Instructions

Create a team.

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": {
      "name": "<name>"
    },
    "name": "webex_create_team"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName
descriptionNoDescription

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

D1.9/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden, yet it discloses nothing beyond the word "Create." It does not state permission requirements, whether the team is returned, what defaults apply, or any limits on team creation.

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?

Two words, front-loaded, with zero filler or redundancy. The problem is under-specification rather than verbosity, so it earns only a middling score for structure.

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

Completeness1/5

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

This is a mutation tool with no annotations, no output schema, and no explanation of authorization or side effects. Given that complexity, a one-phrase description leaves an agent without the information needed to invoke it confidently.

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 both parameters (name, description) are formally documented, which sets the baseline at 3. However, the schema descriptions are bare ("Name", "Description") and the tool description adds no meaning such as naming constraints or whether description is optional in practice.

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

Purpose2/5

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

The description is "Create a team." which merely restates the tool name webex_create_team. It conveys the verb and resource but offers no differentiation from the many sibling creation tools (webex_create_space, webex_create_message, webex_create_webhook) or any notion of what a team is in this API.

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 versus webex_create_space, or what prerequisites (org admin rights, licensing) apply. The agent must infer usage entirely from the name, with no explicit when/when-not or alternative routing.

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

Deploy Server

Other Tools