Skip to main content
Glama
Sign In
Plane MCP Server

Plane MCP Server

by leigangzhang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

delete_customer_property

Remove a customer property and its values from all customer profiles using the property ID.

Instructions

Delete a customer property, and every customer's values for it.

Args: property_id: UUID of the customer property

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "property_id": "<property_id>"
    },
    "name": "delete_customer_property"
  }
}

Input Schema

NameRequiredDescriptionDefault
property_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.11

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description must disclose side effects. It does reveal the key destructive consequence: every customer's values for the property are also deleted. However, it does not mention irreversibility, required permissions, or other potential impacts.

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?

The description is two short sentences plus an Args line, with every word earning its place. The main action is front-loaded and the parameter documentation is compact and clear.

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

Completeness4/5

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

For a simple one-parameter delete tool, it covers the purpose, the affected data, and the parameter meaning. An explicit irreversibility warning would improve completeness, but the cascade warning provides enough context for correct invocation.

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

Parameters4/5

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

The schema only indicates property_id is a required string, while the description adds that it is a UUID of the customer property, providing semantic meaning. With 0% schema description coverage, this extra clarity is valuable.

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 opens with 'Delete a customer property, and every customer's values for it,' using a specific verb and resource. The cascade detail distinguishes it from sibling delete tools like delete_customer or delete_work_item_property.

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 choose this tool over alternatives or what prerequisites might be needed. It simply states the action without context, exclusions, or comparisons to related tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools