Skip to main content
Glama
goto-software

plane-mcp-server

delete_state

Delete a project state by providing its unique state ID and project ID.

Instructions

Delete a state by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUUID of the project
state_idYesUUID of the state

Implementation Reference

  • Handler function that deletes a state by project_id and state_id, using PlaneClient.states.delete()
    @mcp.tool()
    def delete_state(project_id: str, state_id: str) -> None:
        """
        Delete a state by ID.
    
        Args:
            project_id: UUID of the project
            state_id: UUID of the state
        """
        client, workspace_slug = get_plane_client_context()
        client.states.delete(workspace_slug=workspace_slug, project_id=project_id, state_id=state_id)
  • Registration of state tools (including delete_state) via register_state_tools
    register_state_tools(mcp)
  • register_state_tools wraps all state tools including delete_state with @mcp.tool() decorator
    def register_state_tools(mcp: FastMCP) -> None:
  • Helper that provides authenticated PlaneClient and workspace slug used by delete_state handler
    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,
        )
  • Integration test expected tools list includes delete_state to validate it is registered
    "delete_state",
Behavior2/5

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

With no annotations provided, the description must bear the full burden of behavioral disclosure. It only states 'Delete a state by ID' without any information about irrevocability, cascading effects, access control requirements, or typical response. The agent is left uninformed about critical behavioral traits beyond the basic mutation implied by 'Delete'.

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, front-loaded sentence with no redundancy. It is appropriately concise but perhaps excessively brief, missing opportunities to add helpful context without being verbose. It earns its place but does not fully leverage the available space.

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?

Given the simplicity of the tool (two required parameters, no output schema), a minimal description might suffice, but the description omits important context such as what happens after deletion (e.g., cascading effects, irreversibility) or how it relates to other delete operations. This leaves the agent potentially underinformed for safe invocation.

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% (both parameters have descriptions like 'UUID of the project' and 'UUID of the state'), so the schema already explains parameter meaning. The description adds no further semantic value, resulting in a baseline score of 3.

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 ('Delete') and resource ('state') with a specific identifier ('by ID'). However, it does not distinguish this delete operation from the many other delete tools available (e.g., delete_cycle, delete_epic), missing an opportunity to highlight any unique scope or constraints.

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 is provided on when to use this tool versus alternatives. There is no mention of prerequisites, side effects, or conditions under which deletion is appropriate, leaving the agent to infer from the schema alone.

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