Skip to main content
Glama

manage_comments

Destructive

List, add, or delete comments on a TickTick task using the action field; adding requires content, and deleting requires a comment ID and confirmation.

Instructions

List, add or delete comments on a TickTick task. Use action "list", "add" with content, or "delete" with commentId and confirm:true.

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": {
      "action": "<action>",
      "projectId": "<projectId>",
      "taskId": "<taskId>"
    },
    "name": "manage_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
taskIdYesTickTick task ID.
confirmNoMust be true for action "delete" after the user agrees.
contentNoComment text for action "add".
commentIdNoComment ID for action "delete", from a previous list.
projectIdYesTickTick project ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds genuine process behavior by requiring confirm:true and user agreement before deleting. It does not say whether deletes are reversible or what list returns, so the added value is moderate rather than rich.

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?

Two sentences, front-loaded with the capability and immediately followed by the action dispatch guidance. Every clause carries operational information with no filler.

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 three-mode tool with six parameters and no output schema, the description covers mode selection and the guard rail on deletion, which is what an agent most needs. It omits any hint about what list returns or result shape, which is a minor gap.

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 83%, so the schema already documents taskId, projectId, content, commentId, and confirm. The description adds the useful coupling of parameters to actions (content for add, commentId/confirm for delete). Given the high coverage, this sits near the baseline rather than exceeding it substantially.

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 names specific verbs (list, add, delete) and a specific resource (comments on a TickTick task), and scopes it to a single task. This is clearly distinct from every sibling tool (tasks, projects, tags), though it does not explicitly state that differentiation.

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?

It maps each action to its required input: "list", "add" with content, "delete" with commentId and confirm:true. That is effectively when-to-use guidance for the three modes. It lacks any statement of when not to use the tool or of prerequisites (for example, that the task must exist).

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