Skip to main content
Glama

get_membership_details

Retrieve detailed information about a specific Webex membership using its unique ID to manage and organize team interactions effectively.

Instructions

Get details for a membership by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
membershipIdYesThe unique identifier for the membership.

Implementation Reference

  • The main handler function that fetches membership details from the Webex API endpoint /memberships/{membershipId} using a GET request.
    const executeFunction = async ({ membershipId }) => {
    
      try {
        // Construct the URL with the membership ID
        const url = getWebexUrl('/memberships/${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 getting membership details:', error);
        return { error: 'An error occurred while retrieving membership details.' };
      }
    };
  • The input schema definition for the tool, specifying the required 'membershipId' string parameter.
    definition: {
      type: 'function',
      function: {
        name: 'get_membership_details',
        description: 'Get details for a membership by ID.',
        parameters: {
          type: 'object',
          properties: {
            membershipId: {
              type: 'string',
              description: 'The unique identifier for the membership.'
            }
          },
          required: ['membershipId']
        }
      }
    }
  • tools/paths.js:8-8 (registration)
    Specific path entry for this tool in the toolPaths array used for dynamic tool discovery and registration.
    'webex-public-workspace/webex-messaging/get-membership-details.js',
  • lib/tools.js:7-16 (registration)
    The discoverTools function that dynamically imports apiTool from each path in toolPaths and collects them for registration.
    export async function discoverTools() {
      const toolPromises = toolPaths.map(async (file) => {
        const module = await import(`../tools/${file}`);
        return {
          ...module.apiTool,
          path: file,
        };
      });
      return Promise.all(toolPromises);
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a 'Get' operation but doesn't clarify whether it's read-only, requires authentication, has rate limits, or what happens if the membership ID is invalid. The description is minimal and leaves critical behavioral aspects unspecified.

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 with no wasted words. It's appropriately sized for a simple lookup tool and front-loads the essential information.

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 read operation with no annotations and no output schema, the description is insufficient. It doesn't explain what details are returned, potential error conditions, or how this tool fits within the broader membership management context alongside siblings like 'update_membership' and 'delete_membership'.

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% with one parameter fully documented, so the baseline is 3. The description adds no additional meaning beyond what's in the schema (e.g., it doesn't explain format constraints or provide examples for the membershipId).

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 membership by ID', making the purpose understandable. It doesn't explicitly differentiate from sibling tools like 'list_memberships' or 'get_team_membership_details', but the specificity of 'by ID' provides some distinction.

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 'list_memberships' for multiple memberships or 'get_team_membership_details' for team-specific memberships. It lacks any context about prerequisites, typical use cases, or exclusions.

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