Skip to main content
Glama
goto-software

plane-mcp-server

delete_milestone

Delete a milestone from a project by providing its unique milestone ID.

Instructions

Delete a milestone by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUUID of the project
milestone_idYesUUID of the milestone

Implementation Reference

  • The delete_milestone tool handler function. It takes project_id and milestone_id, gets the Plane client context, and calls client.milestones.delete() to delete the milestone.
    def delete_milestone(project_id: str, milestone_id: str) -> None:
        """
        Delete a milestone by ID.
    
        Args:
            project_id: UUID of the project
            milestone_id: UUID of the milestone
        """
        client, workspace_slug = get_plane_client_context()
        client.milestones.delete(workspace_slug=workspace_slug, project_id=project_id, milestone_id=milestone_id)
  • Decorator @mcp.tool() that registers delete_milestone as an MCP tool.
    @mcp.tool()
    def delete_milestone(project_id: str, milestone_id: str) -> None:
  • Registration call: register_milestone_tools(mcp) which includes the delete_milestone tool.
    register_milestone_tools(mcp)
  • Helper function get_plane_client_context() that provides the Plane client instance and workspace slug used by delete_milestone.
    class PlaneClientContext(NamedTuple):
        """Context containing Plane client and workspace information."""
    
        client: PlaneClient
        workspace_slug: str
    
    
    def get_plane_client_context() -> PlaneClientContext:
        """
        Initialize and return a PlaneClient instance with workspace context.
    
        Authentication is handled by the PlaneOAuthProvider, which supports:
        1. Environment variables (PLANE_API_KEY + PLANE_WORKSPACE_SLUG)
        2. HTTP headers (x-api-key + x-workspace-slug)
        3. OAuth access token
    
        Environment variables:
        - PLANE_INTERNAL_BASE_URL: Internal URL for Plane API (preferred for server-to-server calls)
        - PLANE_BASE_URL: Base URL for Plane API (fallback, default: https://api.plane.so)
    
        Returns:
            PlaneClientContext containing configured PlaneClient instance and workspace slug
    
        Raises:
            ConfigurationError: If access token is not available or workspace slug is missing
        """
        base_url = os.getenv("PLANE_INTERNAL_BASE_URL") or os.getenv("PLANE_BASE_URL", "https://api.plane.so")
        workspace_slug = os.getenv("PLANE_WORKSPACE_SLUG", "")
    
        api_key = os.getenv("PLANE_API_KEY", "")
        access_token = None
    
        # Get access token from the OAuth provider (which handles all auth methods)
        stored_access_token: AccessToken | None = get_access_token()
        if stored_access_token:
            # Determine authentication method to use appropriate PlaneClient constructor
            auth_method = stored_access_token.claims.get("auth_method", "oauth")
            token = stored_access_token.token
            workspace_slug = stored_access_token.claims.get("workspace_slug", "")
    
            # For API key auth methods, use api_key parameter; for OAuth, use access_token
            if auth_method in ("api_key_env", "api_key_header"):
                api_key = token
            else:
                access_token = token
    
        if access_token:
            client = PlaneClient(
                base_url=base_url,
                access_token=access_token,
            )
        else:
            client = PlaneClient(
                base_url=base_url,
                api_key=api_key,
            )
    
        return PlaneClientContext(
            client=client,
            workspace_slug=workspace_slug,
        )
Behavior2/5

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

No annotations provided, so description carries full burden. It only states the deletion without disclosing side effects, permissions, reversibility, or impact on associated work items.

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?

Single sentence, no filler, all words contribute to meaning. Efficient and clear.

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?

For a simple delete operation with two parameters and no output schema, the description is functional but lacks explicit confirmation about existence checks or return values. It is adequate but not thorough.

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 coverage is 100% with clear UUID descriptions. Description adds little beyond 'by ID', which maps to milestone_id but does not emphasize the need for project_id. Baseline 3 is appropriate.

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?

Description clearly states the action (delete) and the resource (milestone) with the method (by ID). It distinguishes from sibling tools like create_milestone, update_milestone, and remove_work_items_from_milestone.

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 alternative deletion tools (e.g., delete_cycle, delete_epic). No indication of prerequisites or consequences.

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