Skip to main content
Glama

get_team_membership_details

Retrieve detailed information about a specific team membership in Webex using its unique ID to manage and verify user roles within teams.

Instructions

Get details for a team membership by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
membershipIdYesThe unique identifier for the team membership.

Implementation Reference

  • The main handler function `executeFunction` that fetches team membership details from the Webex API endpoint `/team/memberships/{membershipId}` using a GET request, handles errors, and returns the data or error object.
    const executeFunction = async ({ membershipId }) => {
    
      try {
        // Construct the URL with the membership ID
        const url = getWebexUrl(`/team/memberships/${encodeURIComponent(membershipId)}`);
    
        // Set up headers for the request
        const headers = getWebexHeaders();
    
        // Perform the fetch request
        const response = await fetch(url, {
          method: 'GET',
          headers
        });
    
        // Check if the response was successful
        if (!response.ok) {
          const errorData = await response.json();
          throw new Error(errorData);
        }
    
        // Parse and return the response data
        const data = await response.json();
        return data;
      } catch (error) {
        console.error('Error fetching team membership details:', error);
        return { error: 'An error occurred while fetching team membership details.' };
      }
    };
  • Input schema defining the required `membershipId` parameter as a string.
    parameters: {
      type: 'object',
      properties: {
        membershipId: {
          type: 'string',
          description: 'The unique identifier for the team membership.'
        }
      },
      required: ['membershipId']
    }
  • The `apiTool` export that bundles the handler function, tool name 'get_team_membership_details', description, and schema. This is imported and registered dynamically via tools/paths.js and lib/tools.js.
    const apiTool = {
      function: executeFunction,
      definition: {
        type: 'function',
        function: {
          name: 'get_team_membership_details',
          description: 'Get details for a team membership by ID.',
          parameters: {
            type: 'object',
            properties: {
              membershipId: {
                type: 'string',
                description: 'The unique identifier for the team membership.'
              }
            },
            required: ['membershipId']
          }
        }
      }
    };
    
    export { apiTool };
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 burden of behavioral disclosure. It states this is a 'Get' operation, implying it's likely read-only, but doesn't confirm this or describe any other behavioral traits like error handling, rate limits, authentication needs, or what the returned details include. For a tool with no annotation coverage, this is a significant gap.

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

Conciseness5/5

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

The description is a single, efficient sentence that directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded, making it easy to understand at a glance.

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?

Given the complexity of a tool that retrieves details (likely involving structured data) and the lack of both annotations and an output schema, the description is insufficient. It doesn't explain what details are returned, potential error cases, or behavioral aspects, leaving the agent with incomplete information for proper invocation.

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?

The input schema has 100% description coverage, with the parameter 'membershipId' clearly documented as 'The unique identifier for the team membership.' The description adds no additional meaning beyond this, so it meets the baseline score of 3 where the schema does the heavy lifting.

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

Purpose4/5

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

The description clearly states the verb ('Get') and resource ('details for a team membership by ID'), making the purpose specific and understandable. However, it doesn't explicitly distinguish this tool from its sibling 'get_membership_details', which appears to serve a similar function, leaving some ambiguity about when to use one over the other.

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?

The description provides no guidance on when to use this tool versus alternatives like 'get_membership_details' or 'list_team_memberships'. It lacks context about prerequisites, such as needing a membership ID, and doesn't mention any exclusions or specific scenarios where this tool is preferred.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Kashyap-AI-ML-Solutions/webex-messaging-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server