Skip to main content
Glama

move_tasks

Move up to 50 TickTick tasks from one project to another by specifying source and destination project IDs with the task IDs to transfer.

Instructions

Move up to 50 TickTick tasks from one project to another.

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": {
      "fromProjectId": "<fromProjectId>",
      "toProjectId": "<toProjectId>",
      "taskIds": "<taskIds>"
    },
    "name": "move_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdsYes
toProjectIdYesDestination project ID.
fromProjectIdYesSource project ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false), so the safety bar is lower, but the description adds almost nothing: it does not say whether tasks are removed from the source project, whether the move is atomic if one task ID is invalid, what happens to tasks not in the source, or whether extra permissions are needed. The 'up to 50' cap duplicates the schema's maxItems constraint rather than adding new behavioral context.

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?

A single front-loaded sentence with no filler or redundancy. Its brevity is efficient, though the sparseness edges toward under-specification rather than tight writing.

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

Completeness2/5

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

For a multi-parameter mutation tool with no output schema and only minimal annotations, the description omits key operational details: partial-failure behavior, whether the source project retains the tasks, and any limits or side effects. An agent could invoke it but would not know what to expect on errors or edge cases.

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

Parameters2/5

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

Schema coverage is 67%, with source/destination IDs documented in-schema and taskIds carrying only a maxItems constraint. The description merely restates the direction and the 50-item cap, adding no meaning about ID format, behavior for invalid IDs, or ordering of the taskIds array.

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 and resource (move tasks) plus scope (from one project to another, up to 50). The verb 'move' is distinct from the sibling set of create/update/delete/complete task tools, so an agent can differentiate it. It stops short of naming a sibling or spelling out how it differs from update_task, hence 4 rather than 5.

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?

There is no when-to-use or when-not-to-use guidance and no mention of alternatives such as update_task or filter_tasks for relocating work. The only implicit context is that the operation spans two projects, which an agent gets from the schema anyway.

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