Skip to main content
Glama

list_team_members

Retrieve team members from Fathom-Simple-MCP with pagination and team filtering options to manage and organize team data.

Instructions

Retrieve paginated team members with optional team filtering.

Examples: list_team_members_tool() # Get all team members across all teams list_team_members_tool(team="Engineering") # Filter members by team name list_team_members_tool(cursor="def456") # Paginate through member list

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoPagination cursor
per_pageNoNumber of results per page (default: 50)
teamNoFilter by team name

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler function implementing the list_team_members tool logic: handles parameters, calls Fathom API client.get_team_members, processes pagination/filtering, includes error handling and logging via MCP Context.
    async def list_team_members(
        ctx: Context,
        cursor: Optional[str] = None,
        team: Optional[str] = None,
        per_page: Optional[int] = None
    ) -> dict:
        """Retrieve paginated list of team members with optional team filtering.
        
        Returns team member records that can be used to identify meeting participants
        and recording metadata.
        
        Args:
            ctx: MCP context for logging
            cursor: Pagination cursor from previous response for next page
            team: Filter members by specific team name (case-sensitive)
            per_page: Number of results per page (default: 50, configurable via DEFAULT_PER_PAGE env var)
        
        Returns:
            dict: {
                "items": [Team member objects with name, email, and team associations],
                "limit": int (default 20),
                "cursor": str (for pagination, null if no more results)
            }
        """
        try:
            await ctx.info("Fetching team members from Fathom API")
            
            # Use config default if per_page not provided
            effective_per_page = per_page if per_page is not None else config.default_per_page
            
            # Build parameters
            params = {}
            if cursor:
                params["cursor"] = cursor
            if team:
                params["team"] = team
            params["limit"] = effective_per_page
            
            result = await client.get_team_members(params=params if params else None)
            await ctx.info("Successfully retrieved team members")
    
            return result
            
        except FathomAPIError as e:
            await ctx.error(f"Fathom API error: {e.message}")
            raise e
        except Exception as e:
            await ctx.error(f"Unexpected error fetching team members: {str(e)}")
            raise e
  • server.py:194-209 (registration)
    MCP tool registration for list_team_members using @mcp.tool decorator, defines input schema with Pydantic Field descriptions, delegates execution to tools.team_members.list_team_members.
    @mcp.tool
    async def list_team_members(
        ctx: Context,
        cursor: str = Field(default=None, description="Pagination cursor"),
        per_page: int = Field(default=None, description=f"Number of results per page (default: {config.default_per_page})"),
        team: str = Field(default=None, description="Filter by team name")
    ) -> Dict[str, Any]:
        """Retrieve paginated team members with optional team filtering.
        
        Examples:
            list_team_members_tool()  # Get all team members across all teams
            list_team_members_tool(team="Engineering")  # Filter members by team name
            list_team_members_tool(cursor="def456")  # Paginate through member list
        """
        return await tools.team_members.list_team_members(ctx, cursor, team, per_page)
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses pagination behavior and optional team filtering, but doesn't mention rate limits, authentication requirements, error conditions, or what happens with invalid inputs. It adds some context beyond the schema but leaves behavioral gaps.

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 efficiently structured with a clear purpose statement followed by concrete examples. Every sentence serves a purpose: the first establishes core functionality, and the three examples demonstrate different usage patterns without redundancy. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that an output schema exists (context signals indicate 'Has output schema: true'), the description doesn't need to explain return values. It covers the essential functionality of retrieving and filtering team members with pagination. The main gap is lack of behavioral details like error handling, but for a read-only list operation with good schema coverage, this is reasonably 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%, so the schema already documents all three parameters thoroughly. The description adds minimal value through examples showing usage patterns, but doesn't provide additional semantic context beyond what's in the schema descriptions. Baseline 3 is appropriate given high schema coverage.

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

Purpose5/5

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

The description clearly states the verb 'retrieve' and resource 'team members', specifies pagination behavior, and distinguishes from siblings like 'list_teams' by focusing on members rather than teams. The examples further clarify the scope and filtering capabilities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage through examples showing filtering by team name and pagination, but lacks explicit guidance on when to use this tool versus alternatives like 'list_teams' or other sibling tools. No when-not-to-use scenarios or prerequisites are mentioned.

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

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/druellan/Fathom-Simple-MCP'

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