Skip to main content
Glama

list_teams

Retrieve paginated lists of teams with organizational structure from Fathom meeting data. Use this tool to access team information efficiently with cursor-based pagination.

Instructions

Retrieve paginated list of teams with organizational structure.

Examples: list_teams_tool() # Get first page of teams list_teams_tool(cursor="abc123") # Get next page using cursor

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoPagination cursor
per_pageNoNumber of results per page (default: 50)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core implementation of the list_teams tool handler that fetches paginated teams from the Fathom API.
    async def list_teams(
        ctx: Context,
        cursor: Optional[str] = None,
        per_page: Optional[int] = None
    ) -> dict:
        """Retrieve paginated list of teams in the organization.
        
        Returns team records that can be used for filtering meetings and team members.
        Team names from this endpoint can be used as values for the 'teams' parameter
        in list_meetings and 'team' parameter in list_team_members.
        
        Args:
            ctx: MCP context for logging
            cursor: Pagination cursor from previous response for next page
            per_page: Number of results per page (default: 50, configurable via DEFAULT_PER_PAGE env var)
        
        Returns:
            dict: {
                "items": [Team objects with name and metadata],
                "limit": int (default 20),
                "cursor": str (for pagination, null if no more results)
            }
        """
        try:
            await ctx.info("Fetching teams 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
            params["limit"] = effective_per_page
            
            result = await client.get_teams(params=params if params else None)
            await ctx.info("Successfully retrieved teams")
    
            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 teams: {str(e)}")
            raise e
  • server.py:180-192 (registration)
    Registers the 'list_teams' tool with the MCP server, defines input schema using Pydantic Field annotations, and delegates execution to the core handler in tools/teams.py.
    @mcp.tool
    async def list_teams(
        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})")
    ) -> Dict[str, Any]:
        """Retrieve paginated list of teams with organizational structure.
        
        Examples:
            list_teams_tool()  # Get first page of teams
            list_teams_tool(cursor="abc123")  # Get next page using cursor
        """
        return await tools.teams.list_teams(ctx, cursor, 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 burden of behavioral disclosure. It reveals pagination behavior and provides examples, which is helpful. However, it doesn't cover aspects like rate limits, authentication needs, or error handling, leaving gaps for a mutation-free but operationally complex tool.

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 front-loaded with the core purpose, followed by concise examples that illustrate usage without redundancy. Every sentence earns its place, making it efficient and well-structured.

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 the tool's complexity (pagination, organizational structure) and the presence of an output schema (which handles return values), the description is reasonably complete. It covers the core functionality and usage, though it could benefit from more behavioral context given the lack of annotations.

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 fully documents both parameters. The description adds minimal value beyond the schema by implying pagination usage in examples, but doesn't provide additional semantic context like parameter interactions or constraints.

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 'retrieve' and resource 'paginated list of teams with organizational structure', making the purpose evident. However, it doesn't explicitly differentiate from sibling tools like 'list_team_members' or 'list_meetings', which would require a 5.

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 usage examples but no guidance on when to use this tool versus alternatives like 'list_team_members' or 'search_meetings'. It mentions pagination but doesn't specify contexts where this tool is preferred over siblings.

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