Skip to main content
Glama
goto-software

plane-mcp-server

get_project_members

Retrieve all members of a project by providing its UUID. Useful for team management and access verification.

Instructions

Get all members of a project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUUID of the project
paramsNoOptional query parameters as a dictionary

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The actual handler implementation of the 'get_project_members' tool. It uses the Plane client to fetch project members via the SDK.
    @mcp.tool()
    def get_project_members(project_id: str, params: dict[str, Any] | None = None) -> list[UserLite]:
        """
        Get all members of a project.
    
        Args:
            workspace_slug: The workspace slug identifier
            project_id: UUID of the project
            params: Optional query parameters as a dictionary
    
        Returns:
            List of UserLite objects representing project members
        """
        client, workspace_slug = get_plane_client_context()
        return client.projects.get_members(workspace_slug=workspace_slug, project_id=project_id, params=params)
  • The schema for the return type 'list[UserLite]' used by get_project_members.
    from plane.models.users import UserLite
  • The 'get_project_members' tool is registered indirectly via register_project_tools(mcp) which decorates the function with @mcp.tool().
    def register_tools(mcp: FastMCP) -> None:
        """Register all tools with the MCP server."""
        register_project_tools(mcp)
Behavior2/5

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

With no annotations, the description should disclose behavior like permissions required, pagination, or error handling. It does not, leaving the agent without key safety information.

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

Conciseness4/5

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

The description is very concise—one sentence—but lacks structure like bullet points. No extraneous words, but could be slightly more informative without losing conciseness.

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

Completeness3/5

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

The tool has an output schema, but the description minimally qualifies the response. It covers the basic purpose but omits details on response format or potential errors. Adequate for a simple lookup, but not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, providing baseline 3. However, the description 'Get all members' does not explain the optional 'params' parameter (which can contain query options), so it adds no semantic value beyond the schema.

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 action (get) and resource (members of a project), distinguishing it from sibling get_workspace_members. However, it does not specify if the response includes full objects or just IDs.

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_workspace_members or other list tools. No when-not-to-use or context given.

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/goto-software/plane-mcp-server'

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