Skip to main content
Glama
Google Workspace (GWS) MCP Server

Google Workspace (GWS) MCP Server

tasks_tasks_move

Idempotent

Move a task within its list or to another list, using parent or previous to set its position and destinationTasklist to change lists.

Instructions

Move a task within its list or to another list. Use parent/previous to set position; destinationTasklist to change list.

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": {
      "tasklist": "<tasklist>",
      "task": "<task>"
    },
    "name": "tasks_tasks_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYesTask ID to move
parentNoNew parent task ID (move as subtask under this task)
previousNoNew sibling task ID (move immediately after this task)
tasklistYesSource task list ID
destinationTasklistNoDestination task list ID (omit to move within the source list)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Addedv0.4.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare idempotent=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds that the operation relocates position and/or list, but does not disclose error conditions (e.g., invalid parent, cross-list subtask constraints) or what happens to siblings on reorder.

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?

Two short sentences, front-loaded with the primary action and followed by parameter guidance; almost no waste. Slightly compressed to the point of omitting any return or failure information.

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?

With five fully documented parameters, annotations covering safety, and no output schema required, the description is largely sufficient for correct invocation. Minor gaps remain around ordering semantics when both parent and previous are supplied and around error behavior for cross-list moves.

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 description coverage is 100%, so parameter meaning is already fully documented in the schema, making 3 the baseline. The description's param hints ('parent/previous to set position') largely restate the schema descriptions rather than adding new semantics.

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 a task within its list or to another list,' which is clearly distinct from list/get/insert siblings. It does not explicitly separate itself from tasks_tasks_update, which could also rearrange fields, so it falls short of full sibling differentiation.

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?

Gives implicit guidance by explaining which parameters to use for which intent ('parent/previous to set position; destinationTasklist to change list'), which helps an agent pick behavior. It never states when to prefer this over tasks_tasks_update or mentions prerequisites/constraints.

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