Skip to main content
Glama
Sign In
Google Workspace MCP VE

Google Workspace MCP VE

by HuntsDesk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_task_list

Retrieve the title and last updated timestamp for a specific Google Tasks task list. Provide the task list ID and user email.

Instructions

Fetch metadata for a single Google Tasks task list.

Returns list-level info only (title, last updated); for the list's tasks use list_tasks. Requires the tasks.readonly OAuth scope.

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": {
      "user_google_email": "<user_google_email>",
      "task_list_id": "<task_list_id>"
    },
    "name": "get_task_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_google_emailYesThe user's Google email address (authenticated account).
task_list_idYesTask list ID from list_task_lists.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.0
    • changedInput schema / properties / task_list_id / description
      Previous value: -"The ID of the task list to retrieve."New value: +"Task list ID from list_task_lists."
    • changedInput schema / properties / user_google_email / description
      Previous value: -"The user's Google email address. Required."New value: +"The user's Google email address (authenticated\naccount)."
  2. First observedv1.19.0

TDQS

A4.5/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses return value scope ('list-level info only, title, last updated') and required permissions (OAuth scope). Does not detail potential errors or idempotency, but for a simple read operation, this is sufficient and transparent.

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?

Three sentences, front-loaded with purpose, efficient with no redundant words. Each sentence adds value: purpose, return info with alternative, and authentication requirement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given output schema exists (not shown), description need not detail return structure. Covers input expectations (requires list ID from list_task_lists), contrasts with sibling, and explains scope. Complete for a simple metadata fetch tool.

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 coverage is 100% with descriptions already clear. Description does not add extra parameter meaning beyond schema. Baseline 3 is appropriate.

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?

Clear verb 'Fetch metadata' with specific resource 'single Google Tasks task list'. Distinguishes from sibling 'list_tasks' by stating that for tasks, use that alternative. No ambiguity.

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

Usage Guidelines5/5

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

Explicitly states when to use (get list metadata) and when not to (use list_tasks for tasks). Mentions required OAuth scope (tasks.readonly), which is a key prerequisite. Provides clear guidance for correct invocation.

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