Skip to main content
Glama
Sign In
google-workspace-mcp

google-workspace-mcp

by smk-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

task_move

Reposition a task in Google Tasks under a parent as a subtask or after a previous task in the same list to set hierarchy and order.

Instructions

Reposition a task: under parent (as a subtask) and/or after previous in the same 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": {
      "account": "<account>",
      "task_id": "<task_id>"
    },
    "name": "task_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
parentNo
accountYes
task_idYes
previousNo
tasklist_idNo@default

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.2

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description is expected to disclose behavioral traits. It only states the effect (repositioning) but does not mention side effects (e.g., does it affect subtask relationships?), permissions required, or reversibility. The lack of detail leaves the agent uninformed about consequences.

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 a single, front-loaded sentence with no wasted words. It efficiently conveys the core action and the two placement options.

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?

Given 5 parameters, no output schema, and no annotations, the description is too brief. It omits details about required parameters, the meaning of 'tasklist_id', and the absence of return value or side effects. The tool's behavior is only partially described.

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 0%, so the description must compensate. It adds meaning for 'parent' (as subtask) and 'previous' (after in list), but does not explain 'account', 'task_id', or 'tasklist_id' (though the latter has a default). The explanation is partially helpful but incomplete.

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 uses the specific verb 'Reposition' and identifies the resource as 'task', clearly indicating it moves a task. It distinguishes from siblings like task_update or task_complete by specifying the repositioning action and the two ways to do it (under parent as subtask, after previous).

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 implies usage for repositioning tasks but does not explicitly state when to use this tool vs alternatives like task_update (which could also modify positions) or when not to use it. No exclusions or context are provided.

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