Skip to main content
Glama
Sign In
webex-mcp

webex-mcp

by yuryev89
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

webex_update_space

Modify a Webex space's title, description, visibility, lock status, or announcement setting by providing the space ID.

Instructions

Update 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": {
      "roomId": "<roomId>"
    },
    "name": "webex_update_space"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoNew title
roomIdYesSpace ID
isLockedNoLocked
isPublicNoPublic to org
descriptionNoNew description
isAnnouncementOnlyNoModerators only

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 supplied, so the description carries the full behavioral burden, yet it discloses nothing about required permissions (Webex space updates typically need moderator/owner rights), whether changes are reversible, or what happens to unspecified fields. For a mutation tool this is a complete gap.

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

Conciseness2/5

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

The single sentence is short and front-loaded, but its brevity reflects under-specification rather than economy of expression. There is no wasted wording because there is effectively no content at all.

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?

For a six-parameter mutation tool with no annotations and no output schema, the definition should explain effects, permissions, and return behavior. None of that is present, leaving the agent to guess at consequences of a write operation.

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 names and describes all six parameters (roomId, title, description, isLocked, isPublic, isAnnouncementOnly). The description adds no meaning beyond that, but the high coverage establishes the baseline of 3 per the rubric.

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?

"Update a space" restates the tool name (webex_update_space) without adding any distinguishing detail. It does convey a verb and resource, but gives no hint about which aspects of a space are updatable or how this differs from sibling mutators like webex_update_team or webex_update_membership.

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 when-to-use guidance, no mention of prerequisites, and no reference to alternatives such as webex_create_space or webex_delete_space. An agent must infer entirely from the name that this is the mutation counterpart to webex_get_space.

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