Skip to main content
Glama

delete_project

Destructive

Permanently delete a TickTick project after explicit user confirmation. Use it to remove unwanted projects while preferring to close or move tasks when unsure.

Instructions

Permanently delete a TickTick project. Requires confirm:true; ask the user first. Prefer closing tasks or moving them when unsure.

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": {
      "projectId": "<projectId>"
    },
    "name": "delete_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true after the user agrees to delete.
projectIdYesTickTick project ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, but the description adds the permanence claim and the human-consent gate, which the annotations do not express. The remaining gap is what happens to tasks inside the project (cascade delete vs. orphaning), which is exactly the side effect an agent needs to know before confirming.

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?

Three short sentences with zero waste, and the destructive action plus its confirm gate are front-loaded before the softer fallback advice.

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 full schema coverage and no output schema, almost everything needed is present. The one material omission is the fate of contained tasks, which matters for a project-level delete.

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 both confirm and projectId already described in the schema, so the baseline is 3. The description restates the confirm requirement but adds no new format or constraint detail beyond it.

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?

"Permanently delete a TickTick project" gives a specific verb, resource, and irreversibility qualifier. The resource noun (project vs. task) alone distinguishes it from delete_task and the other siblings without opening any schema.

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

Usage Guidelines5/5

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

It states the precondition (confirm:true), the interaction protocol (ask the user first), and a fallback direction (prefer closing or moving tasks when unsure). That is explicit when-to-use and when-to-avoid guidance rather than an implied context.

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