Skip to main content
Glama

list_tasks

Retrieve tasks from a Google Tasks list with filters for completion, due dates, and pagination. Supports incremental sync via updated_min.

Instructions

List tasks in one task list, with rich filters and auto-pagination.

Auto-paginates internally to fill up to max_results. For one specific task use get_task. For write operations use manage_task. Completed tasks from the web UI / mobile apps are "hidden" by default — to see them set both show_completed=True AND show_hidden=True. Requires the tasks.readonly OAuth scope.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_google_emailYesThe user's Google email address (authenticated account).
task_list_idYesTask list ID from list_task_lists.
max_resultsNoCap on tasks returned across all pages. Default varies; hard cap 10000.
page_tokenNoResume cursor from a prior call's "Next page token".
show_completedNoInclude completed tasks. Default True.
show_deletedNoInclude deleted tasks. Default False.
show_hiddenNoInclude tasks hidden from the UI (required alongside show_completed to see web/mobile-completed tasks). Default False.
show_assignedNoInclude tasks assigned to the user. Default False.
completed_maxNoRFC3339 upper bound on completion date.
completed_minNoRFC3339 lower bound on completion date.
due_maxNoRFC3339 upper bound on due date. Auto-adjusted to include the boundary date's tasks.
due_minNoRFC3339 lower bound on due date.
updated_minNoRFC3339 lower bound on last-modified time — useful for incremental sync.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations, the description fully explains auto-pagination behavior, the hidden completed tasks nuance requiring both show_completed and show_hidden, and the required OAuth scope. This goes beyond basic functionality.

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?

The description is very concise, with two short paragraphs front-loading the purpose. Every sentence provides essential information with no redundancy.

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?

Given the complexity (13 parameters, filters, pagination), the description covers key behavioral aspects: auto-pagination, hidden tasks quirk, OAuth scope, and sibling differentiation. It doesn't detail date filters, but schema descriptions cover them, and output schema exists for return values.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds crucial context beyond schema, particularly the show_completed/show_hidden interaction and auto-pagination. This elevates the score above baseline.

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?

The description clearly states the tool lists tasks in one task list with rich filters and auto-pagination. It distinguishes from sibling tools get_task and manage_task, and specifies the required OAuth scope.

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 guides when to use this tool vs alternatives: 'For one specific task use get_task. For write operations use manage_task.' Also provides a specific caveat about hidden completed tasks and scope requirement.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/HuntsDesk/ve-gws'

If you have feedback or need assistance with the MCP directory API, please join our Discord server