Skip to main content
Glama
Sign In
tick-mcp

tick-mcp

by KpihX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

set_subtask_parent

Set a task's parent to create a subtask, or remove the parent to unlink the subtask relationship. Provide parent_id or old_parent_id accordingly.

Instructions

Set or unset a task's parent (subtask relationship).

[Category: Tasks — Batch]  [Auth: V2]
[Related: create_task, get_task_detail]
[Workflow: create_task → set_subtask_parent (TickTick ignores parentId on creation)]

Args:
    task_id: The child task ID.
    project_id: The project both tasks belong to.
    parent_id: New parent task ID (to make subtask). Provide THIS to SET.
    old_parent_id: Previous parent ID (to remove). Provide THIS to UNSET.
        ⚠️ Provide EITHER parent_id OR old_parent_id, not both.

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": {
      "task_id": "<task_id>",
      "project_id": "<project_id>"
    },
    "name": "set_subtask_parent"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes
project_idYes
parent_idNo
old_parent_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description bears full responsibility. It discloses the behavioral nuance that TickTick ignores parentId on creation, and distinguishes between setting and unsetting a parent. However, it does not mention idempotency, permissions, or potential side effects, which would improve transparency.

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 concise and well-structured, using bold, emojis, and sections. Every sentence adds value, and the formatting enhances readability without unnecessary verbosity.

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

Completeness3/5

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

The tool has no output schema, so the description should detail return behavior or error conditions. It does not mention what the tool returns (e.g., success message or the updated task), nor does it address prerequisites like task existence. This is a notable gap for a mutation tool.

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 has no descriptions (0% coverage), so the description must add meaning. It successfully explains the role of each parameter, including the special constraint that only one of parent_id or old_parent_id should be provided, providing clear semantics beyond the schema.

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?

The description clearly states the tool sets or unsets a subtask relationship, with a specific verb and resource. It distinguishes itself from related tools like create_subtask by noting that TickTick ignores parentId on creation, clarifying when to use this tool instead.

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?

The description provides explicit usage guidelines: a workflow (create_task then set_subtask_parent), and instructions for when to provide parent_id vs old_parent_id, including a warning not to provide both. It lacks comparison to sibling tools but is otherwise clear.

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