Skip to main content
Glama
goto-software

plane-mcp-server

retrieve_epic

Fetch details of a specific epic by providing its project and epic UUIDs.

Instructions

Retrieve an epic by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUUID of the project
epic_idYesUUID of the epic

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
deleted_atNo
created_atNo
updated_atNo
pointNo
nameYes
descriptionNo
description_htmlNo
description_strippedNo
description_binaryNo
priorityNo
start_dateNo
target_dateNo
sequence_idNo
sort_orderNo
completed_atNo
archived_atNo
is_draftNo
external_sourceNo
external_idNo
created_byNo
updated_byNo
projectYes
workspaceYes
parentNo
stateNo
estimate_pointNo
typeNo
assigneesNo
labelsNo

Implementation Reference

  • The actual handler function for the 'retrieve_epic' tool. It takes project_id and epic_id, gets the Plane client context, creates RetrieveQueryParams, and calls client.epics.retrieve().
    @mcp.tool()
    def retrieve_epic(
        project_id: str,
        epic_id: str,
    ) -> Epic:
        """
        Retrieve an epic by ID.
    
        Args:
            project_id: UUID of the project
            epic_id: UUID of the epic
    
        Returns:
            Epic object
        """
        client, workspace_slug = get_plane_client_context()
    
        params = RetrieveQueryParams()
    
        return client.epics.retrieve(
            workspace_slug=workspace_slug,
            project_id=project_id,
            epic_id=epic_id,
            params=params,
        )
  • The 'register_epic_tools' function which, via the '@mcp.tool()' decorator on line 238, registers retrieve_epic as an MCP tool.
    def register_epic_tools(mcp: FastMCP) -> None:
  • The docstring/type hints that serve as the input schema: project_id (str), epic_id (str), returns Epic.
    """
    Retrieve an epic by ID.
    
    Args:
        project_id: UUID of the project
        epic_id: UUID of the epic
    
    Returns:
        Epic object
    """
  • The helper function get_plane_client_context() is called to obtain the client and workspace_slug.
    client, workspace_slug = get_plane_client_context()
    
    params = RetrieveQueryParams()
    
    return client.epics.retrieve(
        workspace_slug=workspace_slug,
        project_id=project_id,
        epic_id=epic_id,
        params=params,
    )
  • The top-level registration call: register_epic_tools(mcp) which triggers the registration of retrieve_epic along with other epic tools.
    register_epic_tools(mcp)
Behavior2/5

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

No annotations are provided, and the description does not disclose any behavioral traits (e.g., read-only, authentication needs, or output structure). The burden falls entirely on the description, which fails to add value beyond the tool name.

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 a single sentence that is front-loaded and to the point. It is appropriately sized for a simple retrieval tool, though it could include more detail without becoming verbose.

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?

Despite a high schema coverage and presence of an output schema, the description omits mention of required parameters (both project_id and epic_id) and does not clarify how this tool differs from many similar sibling tools.

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 descriptions cover 100% of parameters with clear definitions (UUIDs). The description adds no additional meaning, so baseline of 3 is appropriate.

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 (Retrieve) and resource (an epic) but does not specify the need for both project_id and epic_id; however, the schema compensates to some extent.

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?

No guidance on when to use this tool versus alternatives like list_epics or other retrieve tools; no exclusions or context 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/goto-software/plane-mcp-server'

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