google-workspace-mcp-advanced

move_task

Move a task to a new parent or position within its list, or transfer it to a different task list, with dry-run support for safe preview.

Instructions

Move a task to a different position or parent within the same list, or to a different list.

Args: user_google_email (str): The user's Google email address. Required. task_list_id (str): The ID of the current task list containing the task. task_id (str): The ID of the task to move. parent (Optional[str]): New parent task ID (for making it a subtask). previous (Optional[str]): Previous sibling task ID (for positioning). destination_task_list (Optional[str]): Destination task list ID (for moving between lists). dry_run (bool): When True (default), return planned mutation without executing.

Returns: str: Confirmation message with updated task details.

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": {
      "user_google_email": "<user_google_email>",
      "task_list_id": "<task_list_id>",
      "task_id": "<task_id>"
    },
    "name": "move_task"
  }
}

Input Schema

Name	Required	Description	Default
`user_google_email`	Yes
`task_list_id`	Yes
`task_id`	Yes
`parent`	No
`previous`	No
`destination_task_list`	No
`dry_run`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.10Jun 2, 2026

TDQS

A4.5/5.0

Behavior4/5

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

No annotations are present, so the description carries the full burden. It explains the core behavior, including the ability to change parent or previous sibling, and move between lists. It also discloses the dry_run behavior (default true, returns planned mutation). Some details like permission requirements or side effects on subtasks are omitted, but overall adequate.

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?

The description is well-structured: a one-line summary followed by parameter descriptions. It is front-loaded with the main purpose. While slightly lengthy, every sentence adds value. Could be more concise, but not excessively verbose.

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

Completeness5/5

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

Given the tool's complexity (7 parameters, multiple modes), the description covers all relevant aspects: the different move operations, parameter explanations, and the dry_run feature. An output schema exists, so return details are not needed. The description is fully sufficient.

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?

With 0% schema description coverage, the description provides full semantics for all 7 parameters. Each parameter is explained (e.g., 'New parent task ID', 'Previous sibling task ID', 'Destination task list ID'), adding substantial value beyond the schema's type definitions.

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 'Move a task to a different position or parent within the same list, or to a different list.' It uses precise verbs and nouns, distinguishing it from sibling tools like create_task, update_task, and delete_task.

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 explicitly outlines the scenarios: moving within the same list (changing position or parent) or to a different list. It also mentions the dry_run option for testing. However, it does not explicitly state when not to use this tool or point to alternatives.

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

Deploy Server