Skip to main content
Glama

get_people

Retrieve team member data including IDs, names, roles, contact details, and activity dates from Productive.io with optional pagination controls.

Instructions

Get all team members/people with optional pagination.

Returns team member data including:

  • Person ID, name, and email

  • Role and title information

  • Last seen and join dates

  • Avatar and contact information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_numberNoPage number for pagination
page_sizeNoOptional number of people per page (max 200)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool registration and handler for 'get_people'. Includes schema definition via Annotated parameters for pagination. Delegates to the tools module implementation.
    @mcp.tool
    async def get_people(
        ctx: Context,
        page_number: Annotated[int, Field(description="Page number for pagination")] = None,
        page_size: Annotated[
            int, Field(description="Optional number of people per page (max 200)")
        ] = None,
    ) -> Dict[str, Any]:
        """Get all team members/people with optional pagination.
    
        Returns team member data including:
        - Person ID, name, and email
        - Role and title information
        - Last seen and join dates
        - Avatar and contact information
        """
        return await tools.get_people(
            ctx,
            page_number=page_number,
            page_size=page_size,
        )
  • Primary helper function executing the tool logic: builds API parameters (pagination, sort by last_seen_at), calls productive_client.get_people, applies response filtering, handles API and general errors.
    async def get_people(ctx: Context, page_number: int = None, page_size: int = config.items_per_page) -> ToolResult:
        """List all team members/people with optional pagination.
    
        Developer notes:
        - Supports pagination with configurable default page[size].
        - Sorts by most recent activity first.
        - Applies utils.filter_response to sanitize output.
        - Returns basic info for all team members (name, email, role, etc.).
        """
        try:
            await ctx.info("Fetching all people")
            params = {}
            if page_number is not None:
                params["page[number]"] = page_number
            params["page[size]"] = page_size
            params["sort"] = "-last_seen_at"
    
            result = await client.get_people(params=params if params else None)
            await ctx.info("Successfully retrieved people")
    
            filtered = filter_response(result)
    
            return filtered
    
        except ProductiveAPIError as e:
            await _handle_productive_api_error(ctx, e, "people")
        except Exception as e:
            await ctx.error(f"Unexpected error fetching people: {str(e)}")
            raise e
  • Low-level client method that performs the HTTP GET request to the Productive API /people endpoint with optional query parameters.
    async def get_people(self, params: Optional[dict] = None) -> Dict[str, Any]:
        """Get all people/team members"""
        return await self._request("GET", "/people", params=params)
Behavior3/5

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

With no annotations provided, the description carries full burden. It mentions optional pagination and the data structure returned, which is helpful. However, it doesn't disclose behavioral aspects like rate limits, authentication requirements, error conditions, or whether this is a read-only operation (though implied by 'Get').

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 a bulleted list of return data. Every sentence earns its place, with no redundant information. The bullet points make the return format easily scannable.

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 has an output schema (which handles return values), 100% parameter schema coverage, and no annotations, the description provides good context about what data is returned and the pagination capability. However, for a tool with no annotations, it could better address behavioral aspects like rate limits or authentication needs.

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 fully documents both parameters. The description mentions 'optional pagination' which aligns with the schema but adds no additional semantic context beyond what the schema provides. Baseline 3 is appropriate when schema does the heavy lifting.

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 'Get' and the resource 'all team members/people', specifying it returns comprehensive team member data. It distinguishes from sibling tools like 'get_person' (singular) by emphasizing it retrieves multiple people, and from 'quick_search' by focusing on complete team listings rather than filtered searches.

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 for retrieving team member lists with pagination, but doesn't explicitly state when to use this versus alternatives like 'get_person' for single members or 'quick_search' for filtered results. No guidance on prerequisites or exclusions is provided.

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/Productive-GET-MCP'

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