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

Google Workspace (GWS) MCP Server

tasks_tasklists_insert

Creates a new Google Tasks list with a specified title, letting you organize and group related tasks in Google Workspace.

Instructions

Create a new task 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": {
      "title": "<title>"
    },
    "name": "tasks_tasklists_insert"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesTask list title

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.1/5.0
Behavior2/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 mutation and safety profile is covered. The description adds nothing on top of that — notably it does not warn that non-idempotent insertion means duplicate titles produce duplicate lists, nor what the call returns. With annotation coverage present but zero added context, a 2 is warranted.

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?

One short sentence, front-loaded with the verb, with no filler or repetition. For a one-parameter tool the size is appropriate, even if brevity is bought at the cost of detail elsewhere.

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 is simple (one required string, no nesting, no output schema), and annotations cover the safety profile, so little is strictly needed. Still, an agent would benefit from knowing that duplicates are permitted, what the response contains, and whether the creator needs any authorization; those gaps leave it only minimally adequate.

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?

There is a single required parameter with 100% schema description coverage ("Task list title"), so the schema fully documents it. The description contributes no extra meaning such as length limits, uniqueness expectations, or whether an empty title is rejected; baseline 3 applies when the schema carries the load.

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 states a specific verb and resource ("Create a new task list"), which cleanly separates it from a tool that creates a task rather than a list. It stops short of naming or contrasting any sibling such as tasks_tasklists_update or tasks_tasks_insert, so the disambiguation is only implied by the noun.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this versus alternatives, no mention that an existing list can be created repeatedly, and no prerequisites noted. The agent must infer from the tool name alone that this is for creating containers, not for adding tasks.

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