Skip to main content
Glama
iTvX

Google Workspace MCP — Gmail edition

by iTvX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

manage_tasks

Create, update, complete, and delete Google Tasks and task lists across linked accounts, so you can track to-dos alongside Gmail.

Instructions

Manage task lists and tasks in Google Tasks.

Input Schema

NameRequiredDescriptionDefault
dueNoDue date (RFC 3339, e.g. 2026-07-20T00:00:00.000Z — Google stores the date, not the time)
emailYesAccount email address. On list operations, "all" runs it once for every configured account.
notesNoTask notes / details
titleNoOn `createTaskList`, the task list name. On `create` and `update`, the task title.
statusNoTask status
taskIdNoTask ID
operationYeslistTaskLists: list all task lists | getTaskList: get a task list by ID | createTaskList: create a new task list | deleteTaskList: delete a task list and all its tasks | list: list tasks in a task list | get: get a specific task | create: create a new task | update: update a task (patch semantics — only the fields you pass are changed) | complete: mark a task as completed | delete: delete a task
maxResultsNoMax tasks to return (default: 20, max: 100)
taskListIdNoTask list ID (use `listTaskLists` to find)
showCompletedNoInclude completed tasks (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.8.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing about destructive operations, permissions, account selection, patch semantics, or return behavior. It is not misleading, but it adds almost no behavioral context beyond the domain label.

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 a single front-loaded sentence with no filler. It is efficiently concise, though its brevity encodes under-specification rather than deliberate compression.

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?

For a ten-parameter, multi-operation tool with destructive operations and no annotations or output schema, the description is far too thin. The schema compensates on parameter meanings, but an agent still lacks high-level guidance on operation selection, side effects, and account scoping.

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 ten parameters are already documented richly in the schema, including operation meanings, email=all behavior, and patch semantics for update. The description itself adds no parameter semantics, which is acceptable given the schema baseline.

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 names the specific resource and domain: task lists and tasks in Google Tasks. The verb 'manage' is broad, but the resource is clear enough to distinguish this from siblings like manage_calendar or manage_email. It does not differentiate among the tool's many operations, but the schema does that.

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?

The description gives no when-to-use or when-not-to-use guidance, no alternatives, and no prerequisites. An agent must infer entirely from the operation enum that this is the Google Tasks CRUD tool.

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