Skip to main content
Glama
Sign In
google-services-mcp

google-services-mcp

by nabheet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List tasks

google_tasks_list

Retrieve tasks from a Google Tasks list, defaulting to the primary list, with optional due-date filters and pagination.

Instructions

List tasks in a task list (default list if not specified).

Input Schema

NameRequiredDescriptionDefault
accountNoAccount nickname to use.
dueAfterNoOnly tasks due at or after this RFC3339 datetime.
dueBeforeNoOnly tasks due at or before this RFC3339 datetime.
pageTokenNoPage token from a previous result's nextPageToken.
tasklistIdNoTask list ID (default @default).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.95
    • addedInput schema / properties / pageToken
      Added value: +{
+  "description": "Page token from a previous result's nextPageToken.",
+  "type": "string"
+}
  2. Changed2 schema fields changedv0.1.60
    • addedInput schema / properties / dueAfter
      Added value: +{
+  "description": "Only tasks due at or after this RFC3339 datetime.",
+  "type": "string"
+}
    • addedInput schema / properties / dueBefore
      Added value: +{
+  "description": "Only tasks due at or before this RFC3339 datetime.",
+  "type": "string"
+}
  3. Changed1 schema field changedv0.1.30
    • removedInput schema / additionalProperties
      Removed value: -false
  4. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. 'List' implies a read-only operation, but the description says nothing about pagination behavior (despite pageToken existing), what fields are returned, ordering, or whether completed tasks are included. For a 5-parameter tool this leaves notable behavioral gaps.

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?

A single short sentence with zero waste, front-loading the action and resource. Nothing in it is redundant padding.

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?

For a simple read-only list operation with fully documented parameters and no output schema, the description is minimally sufficient, but it omits filtering/pagination context that would help an agent use the dueAfter/dueBefore and pageToken parameters together.

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 five parameters (account, dueAfter, dueBefore, pageToken, tasklistId) are already documented in the schema. The description only restates the default tasklistId behavior, adding no semantics beyond what structured data provides; 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 in a task list') and clarifies the default target list. It does not explicitly distinguish itself from the sibling google_tasks_list_lists (which lists the lists themselves), so an agent must infer that difference from the name, but the purpose 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 Guidelines2/5

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

No guidance on when to use this versus alternatives such as google_tasks_list_lists or how to combine it with google_tasks_complete. The only contextual hint is the parenthetical default-list behavior, which is usage of a parameter rather than selection guidance.

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