Skip to main content
Glama

complete_tasks

Mark one or multiple tasks as complete in TickTick. Provide project and task IDs to finish tasks individually or in batches.

Instructions

Mark one or more tasks as complete.

Supports both single task and batch completion. For single task, you can pass a dictionary directly. For multiple tasks, pass a list of dictionaries.

Args: tasks: Task dictionary or list of task dictionaries. Each task must contain: - project_id (required): ID of the project - task_id (required): ID of the task

Examples: # Single task {"project_id": "xyz789", "task_id": "abc123"}

# Multiple tasks
[
    {"project_id": "xyz789", "task_id": "abc123"},
    {"project_id": "xyz789", "task_id": "def456"},
    {"project_id": "abc123", "task_id": "ghi789"}
]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tasksYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, and the description only covers the input format. It does not disclose side effects, permission requirements, reversibility, or response behavior. The mutation is implied by 'complete' but no additional behavioral context is given.

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 well-structured: a one-line summary, a usage note, and a formatted Args section with examples. Every sentence adds value, and the examples make the structure instantly understandable. No fluff.

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?

The description thoroughly documents the one parameter and its required subfields, and an output schema exists (though not shown) so return values don't need to be explained. It lacks details on preconditions or error cases, but for a simple completion tool this is acceptable.

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

Parameters5/5

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

The input schema is generic (an object or array of string maps), providing zero coverage of the required fields. The description compensates fully by specifying that each task must contain project_id and task_id, and by showing concrete examples for both single and batch cases.

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 'Mark one or more tasks as complete' with a specific verb and resource. It also highlights batch support, but does not explicitly distinguish from sibling tools like update_tasks or ticktick_status, so it stops short of a 5.

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

Usage Guidelines3/5

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

The description explains how to pass single vs. multiple tasks (dictionary vs. list) and provides examples, giving clear usage context. However, it does not mention when to prefer this tool over alternatives or any exclusions, making the guidance implied rather than explicit.

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/Code-MonkeyZhang/ticktick-mcp-enhanced'

If you have feedback or need assistance with the MCP directory API, please join our Discord server