Skip to main content
Glama
mstfe

Google Tasks MCP Server

by mstfe

list_tasks

Retrieve all tasks from the default task list in Google Tasks to view and manage your to-do items.

Instructions

List all tasks in the default task list

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler logic for the 'list_tasks' tool. Calls the Google Tasks API to list tasks in the default tasklist and returns the result as formatted JSON text in the tool response.
    if (request.params.name === "list_tasks") {
      try {
        const response = await tasks.tasks.list({
          tasklist: "@default",
        });
    
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(response.data.items, null, 2),
            },
          ],
        };
      } catch (error) {
        throw new McpError(
          ErrorCode.InternalError,
          `Tasks API error: ${error}`
        );
      }
    }
  • src/index.ts:154-161 (registration)
    Registration of the 'list_tasks' tool in the ListToolsRequestSchema handler, including its name, description, and input schema (which expects no parameters).
    {
      name: "list_tasks",
      description: "List all tasks in the default task list",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Input schema definition for the 'list_tasks' tool, specifying an empty object (no required parameters).
    inputSchema: {
      type: "object",
      properties: {},
    },
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states this lists 'all tasks' but doesn't clarify what 'all' means (e.g., completed vs. pending, pagination limits, or sorting). For a read operation with zero annotation coverage, this leaves significant gaps in understanding the tool's behavior.

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 a single, efficient sentence that communicates the core purpose without any wasted words. It's front-loaded with the essential information and appropriately sized for a simple tool with no parameters.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. However, for a listing operation, it should ideally mention what 'all tasks' includes (e.g., status filters, limits) or the return format, especially since there's no output schema to clarify this.

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?

The input schema has 0 parameters with 100% coverage, so there's no parameter documentation burden. The description appropriately doesn't waste space discussing nonexistent parameters, earning a baseline score of 4 for not adding unnecessary information.

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 clearly states the action ('List') and resource ('tasks in the default task list'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'complete_task' or 'create_task', but the verb 'List' inherently distinguishes it from mutation operations.

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 provides no guidance on when to use this tool versus alternatives. While it's obvious this is for listing tasks rather than creating or deleting them, it doesn't mention whether this should be used for initial discovery, how it relates to filtering or searching capabilities, or any prerequisites for accessing the default task list.

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/mstfe/mcp-google-tasks'

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