Skip to main content
Glama
goto-software

plane-mcp-server

delete_work_item_property

Remove a specified property from a work item type in a project by providing the project, type, and property IDs.

Instructions

Delete a work item property by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUUID of the project
type_idYesUUID of the work item type
work_item_property_idYesUUID of the property

Implementation Reference

  • The actual handler function that implements the 'delete_work_item_property' tool. It gets the Plane client context and calls client.work_item_properties.delete() to delete a work item property by ID.
    @mcp.tool()
    def delete_work_item_property(
        project_id: str,
        type_id: str,
        work_item_property_id: str,
    ) -> None:
        """
        Delete a work item property by ID.
    
        Args:
            workspace_slug: The workspace slug identifier
            project_id: UUID of the project
            type_id: UUID of the work item type
            work_item_property_id: UUID of the property
        """
        client, workspace_slug = get_plane_client_context()
        client.work_item_properties.delete(
            workspace_slug=workspace_slug,
            project_id=project_id,
            type_id=type_id,
            work_item_property_id=work_item_property_id,
        )
  • The registration function that wraps all work item property tools. The @mcp.tool() decorator on line 255 registers 'delete_work_item_property' as an MCP tool.
    def register_work_item_property_tools(mcp: FastMCP) -> None:
        """Register all work item property-related tools with the MCP server."""
  • The input schema for the tool - takes project_id (str), type_id (str), and work_item_property_id (str) as parameters. Returns None.
    def delete_work_item_property(
        project_id: str,
        type_id: str,
        work_item_property_id: str,
    ) -> None:
  • Uses the 'get_plane_client_context' helper function to get the authenticated Plane client and workspace slug.
    client, workspace_slug = get_plane_client_context()
    client.work_item_properties.delete(
        workspace_slug=workspace_slug,
        project_id=project_id,
        type_id=type_id,
        work_item_property_id=work_item_property_id,
    )
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It does not mention irreversibility, cascading effects, or required permissions. For a delete operation, this is insufficient.

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

Conciseness3/5

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

The description is a single sentence, which is concise, but it lacks important details that would earn its place. It is not overly long but is too minimal.

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 tool's simplicity (3 params, no output schema), the description is too sparse. It does not explain what a work item property is or link to related tools like retrieve or list, limiting understanding.

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?

Input schema has 100% description coverage, so each parameter is documented. The description adds no extra meaning beyond the schema, which is adequate at baseline.

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 the resource ('work item property by ID'). However, it does not differentiate this tool from other delete operations among siblings, which is a minor gap.

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, prerequisites, or consequences. The description is purely declarative without usage context.

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