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

Google Workspace (GWS) MCP Server

tasks_tasks_list

Read-only

List tasks in a task list with due/completion date filters and pagination; hidden and assigned tasks are excluded by default, so enable flags to include them.

Instructions

List tasks in a task list. Excludes hidden and assigned tasks by default; set showHidden/showAssigned to include them.

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

Input Schema

NameRequiredDescriptionDefault
dueMaxNoUpper bound on due date (RFC 3339)
dueMinNoLower bound on due date (RFC 3339)
tasklistYesTask list ID (use "@default" for the default list)
pageTokenNoToken for the next page of results
maxResultsNoMax tasks per page (1-100, default 20)
showHiddenNoInclude hidden (cleared) tasks
updatedMinNoLower bound on last-modified time (RFC 3339)
showDeletedNoInclude deleted tasks
completedMaxNoUpper bound on completion date (RFC 3339)
completedMinNoLower bound on completion date (RFC 3339)
showAssignedNoInclude tasks assigned from Docs/Chat Spaces
showCompletedNoInclude completed tasks (default true; ignored unless showHidden is also true)

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

A3.6/5.0
Behavior3/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries most of the burden; it does add genuinely useful behavior by disclosing that hidden and assigned tasks are excluded by default. Beyond that it says nothing about pagination semantics, ordering, or the fact that showCompleted is ignored unless showHidden is set, leaving behavioral gaps for a 12-parameter read tool.

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?

Two sentences, zero waste, with the non-obvious default-exclusion behavior front-loaded ahead of the opt-in flags. Nothing needs trimming or reordering.

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

Completeness4/5

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

For a list tool with a fully described 12-parameter schema and no output schema, the description covers the one surprising default (hidden and assigned tasks excluded). The remaining gap is minor: it does not note that results are paged or that the completed-task filter is gated behind showHidden.

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 every parameter including showHidden, showAssigned, and the ignored-unless-showHidden caveat on showCompleted is already documented. The description restates two flags the schema already explains, adding no format or interaction detail beyond it, so the 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?

States a specific verb and resource (list tasks) and names the required scope (in a task list), which separates it from tasks_tasklists_list and from the single-task tools like tasks_tasks_get. It does not explicitly name an alternative, but the resource is unambiguous.

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?

Usage is implied by the filtering defaults rather than stated: it tells you to set showHidden/showAssigned to widen results but never says when to prefer this tool over tasks_tasks_get or tasklists_list, nor any prerequisites such as needing a valid tasklist ID.

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