Skip to main content
Glama
Sign In
webex-mcp

webex-mcp

by yuryev89
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

webex_remove_membership

Removes a member from a Webex space by membership ID, helping you revoke access or clean up space membership.

Instructions

Remove space member.

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

Input Schema

NameRequiredDescriptionDefault
membershipIdYesMembership ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses essentially nothing beyond the word 'remove'. It does not state whether access is revoked immediately, whether removal is reversible or requires re-invitation, what permissions are needed, or what happens to the removed member's content in the space.

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?

Three words, front-loaded with the verb and free of any waste. The brevity is not padding, but it crosses into under-specification rather than efficient concision, so it cannot score higher.

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 structurally simple (one required param, no nested objects, no output schema), so expectations are moderate. Still, as an unannotated destructive mutation whose return value is undocumented, the definition leaves an agent without enough to call it safely or correctly.

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% for the single required parameter, so the baseline of 3 applies. The description does not clarify that membershipId is a Webex membership resource ID rather than a personId or spaceId, which would be the only genuinely useful addition here.

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?

States a verb (remove) and a resource (space member), so the operation type is discernible. However, it gives no scope or identity detail and does not distinguish itself from the near-identical sibling webex_remove_team_membership or clarify its relationship to webex_list_memberships / webex_delete_space.

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 (e.g. caller must be a space moderator), and no pointer to alternatives such as webex_update_membership or webex_remove_team_membership. The agent must infer the entire selection context from the name alone.

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