Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Delete a card (Bug, User Story, Feature, or Epic)

delete_card

Delete a Targetprocess card by ID across Bugs, User Stories, Features, and Epics. Verify the card type first via search when uncertain to avoid removing the wrong entity.

Instructions

Delete (remove) a Targetprocess card by its ID. Works on Bugs, User Stories, Features, and Epics. IF the type is uncertain, resolve it first via "search_tp_cards" or by fetching the card.

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": {
      "id": "<id>",
      "type": "<type>"
    },
    "name": "delete_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe card ID to delete (e.g. 148980)
typeYesThe entity type of the card being deleted

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description carries the entire behavioral burden, and it discloses almost nothing beyond the verb: no statement that deletion is irreversible, no mention of whether related entities (relations, comments, test cases) are removed, and no permission or failure-mode notes. Only the bare fact of removal is conveyed.

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?

Three short sentences, front-loaded with the verb and target, then scope, then the conditional prerequisite. The only redundancy is the parenthetical "(remove)" after "Delete."

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 two-parameter destructive tool with a fully documented schema and no output schema, the definition covers what it does and how to disambiguate the type. The notable gap is the absence of any consequence or irreversibility note for a delete operation, which is the main thing an agent still needs.

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 per-parameter descriptions and an enum, so the baseline is 3. The description does add one useful semantic point for the type parameter — verify it with search_tp_cards when uncertain — but adds nothing about id format or behavior.

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?

States a specific verb+resource ("Delete a Targetprocess card by its ID") and enumerates the valid entity types, which mirrors the enum and separates it from relation- or step-deletion siblings. It stops short of explicitly contrasting itself with delete_card_relation or delete_test_case_step_by_id, so not a full 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete routing guidance: if the card type is uncertain, resolve it first via search_tp_cards or by fetching the card — a genuine precondition tied to the required enum parameter. It does not say when NOT to delete (e.g., prefer state change over deletion), so it falls short of a 5.

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