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

Google Workspace (GWS) MCP Server

tasks_tasks_insert

Create a new task in a Google Tasks list, with optional due date, notes, status, parent task for nesting, or previous sibling for ordering.

Instructions

Create a new task. Use parent to nest as a subtask, previous to position after a sibling.

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>",
      "title": "<title>"
    },
    "name": "tasks_tasks_insert"
  }
}

Input Schema

NameRequiredDescriptionDefault
dueNoDue date (RFC 3339, e.g. "2026-06-01T00:00:00.000Z")
notesNoFree-text notes / body
titleYesTask title
parentNoParent task ID (insert as a subtask under this task)
statusNoTask status: needsAction or completed
previousNoSibling task ID (insert immediately after this task)
tasklistYesTask list ID to insert into

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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds only the nesting/positioning behavior, which is arguably read off the schema; it says nothing about whether the created task is returned, how parent/previous interact, or what happens with an invalid ID. No contradiction with annotations.

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 with the core action front-loaded and no filler. The second sentence is compressed to the point of being slightly telegraphic, but nothing is wasted.

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?

For a seven-parameter creation tool with no output schema, the definition covers the action and the two structural parameters but omits the required fields (title, tasklist), any mention of the returned object, and any interaction rules between parent and previous. Annotations carry the safety profile, so the remaining gap is moderate rather than severe.

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 all seven parameters, including parent and previous, are already documented in the schema. The description restates the meaning of parent and previous rather than adding new detail such as precedence when both are supplied or how due/status formats behave. Baseline 3 applies.

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?

The description opens with a specific verb+resource pairing, "Create a new task," which is unambiguous and clearly separates it from reads and mutations in the sibling set. It stops short of naming the natural counterpart (tasks_tasks_update) or clarifying that this is not for task lists, so sibling differentiation is only implicit.

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?

"Use parent to nest as a subtask, previous to position after a sibling" tells the agent how to use two optional parameters, which is useful context, but there is no guidance on when to choose this tool versus tasks_tasks_update or tasks_tasks_move, and no stated prerequisites such as needing an existing tasklist ID.

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