Skip to main content
Glama
Sign In
webex-mcp

webex-mcp

by yuryev89
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

webex_get_team_membership

Retrieve details for a specific Webex team membership by its ID, letting you verify who belongs to a team and manage team access.

Instructions

Get team membership by ID.

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_get_team_membership"
  }
}

Input Schema

NameRequiredDescriptionDefault
membershipIdYesTeam membership ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.6/5.0
Behavior2/5

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

There are no annotations, so the description carries the full behavioral burden, yet 'Get' is the only signal that this is a read-only operation. It says nothing about permission requirements, what happens when the membership ID does not exist, or what the response contains.

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

Conciseness4/5

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

One short, front-loaded sentence with no filler or redundancy. It is efficient, though efficiency here partly reflects how little information was supplied.

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?

For a simple one-parameter read this is thin: with no annotations and no output schema, the agent gets no picture of the return shape, error behavior, or authorization needs. A sentence covering those would make this complete.

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% and the single membershipId parameter is documented in the schema as 'Team membership ID'. The description adds only 'by ID', which contributes no meaning beyond the schema, so the baseline 3 applies.

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?

The description names a verb (Get) and resource (team membership), which is enough to infer a single-item read. However, it never distinguishes itself from the very close sibling webex_get_membership (space membership) or from webex_list_team_memberships, so the agent must infer 'team vs space' and 'get vs list' from the tool name alone.

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?

No when-to-use guidance, no mention of when to prefer webex_list_team_memberships, and no prerequisites such as needing the membership ID from a list call first. The description simply restates the operation.

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