Skip to main content
Glama
arpitbatra123

Google Tasks MCP Server

list-tasklists

Retrieve all task lists from Google Tasks to view, organize, or manage your tasks through Claude's interface.

Instructions

List all task lists

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:188-242 (registration)
    Registration of the 'list-tasklists' tool with inline handler implementation that lists all task lists from Google Tasks API after checking authentication.
    server.tool("list-tasklists", "List all task lists", {}, async () => {
      if (!isAuthenticated()) {
        return {
          isError: true,
          content: [
            {
              type: "text",
              text: "Not authenticated. Please use the 'authenticate' tool first.",
            },
          ],
        };
      }
    
      try {
        const response = await tasks.tasklists.list();
        const taskLists = response.data.items || [];
    
        if (taskLists.length === 0) {
          return {
            content: [
              {
                type: "text",
                text: "No task lists found.",
              },
            ],
          };
        }
    
        const formattedLists = taskLists.map((list) => ({
          id: list.id,
          title: list.title,
          updated: list.updated,
        }));
    
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(formattedLists, null, 2),
            },
          ],
        };
      } catch (error) {
        console.error("Error listing task lists:", error);
        return {
          isError: true,
          content: [
            {
              type: "text",
              text: `Error listing task lists: ${error}`,
            },
          ],
        };
      }
    });
  • The handler function for 'list-tasklists' tool: authenticates, calls tasks.tasklists.list(), formats the response, and returns JSON or appropriate error messages.
    server.tool("list-tasklists", "List all task lists", {}, async () => {
      if (!isAuthenticated()) {
        return {
          isError: true,
          content: [
            {
              type: "text",
              text: "Not authenticated. Please use the 'authenticate' tool first.",
            },
          ],
        };
      }
    
      try {
        const response = await tasks.tasklists.list();
        const taskLists = response.data.items || [];
    
        if (taskLists.length === 0) {
          return {
            content: [
              {
                type: "text",
                text: "No task lists found.",
              },
            ],
          };
        }
    
        const formattedLists = taskLists.map((list) => ({
          id: list.id,
          title: list.title,
          updated: list.updated,
        }));
    
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(formattedLists, null, 2),
            },
          ],
        };
      } catch (error) {
        console.error("Error listing task lists:", error);
        return {
          isError: true,
          content: [
            {
              type: "text",
              text: `Error listing task lists: ${error}`,
            },
          ],
        };
      }
    });
  • Empty schema object indicating no input parameters required for the tool.
    server.tool("list-tasklists", "List all task lists", {}, async () => {
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('List all') but lacks details on permissions, rate limits, pagination, or response format. This is a significant gap for a tool that likely returns multiple items.

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 with zero waste. It is front-loaded and directly conveys the core functionality without redundancy or fluff, making it highly concise and well-structured.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It doesn't address behavioral aspects like pagination, ordering, or error handling, which are crucial for a list operation. The minimal description fails to compensate for the missing structured data.

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 no parameter documentation is needed. The description appropriately omits parameter details, aligning with the schema. A baseline of 4 is applied as it doesn't add 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 'List all task lists' clearly states the verb ('List') and resource ('task lists'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'get-tasklist' or 'list-tasks', but the resource specificity provides adequate clarity.

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 is provided on when to use this tool versus alternatives like 'get-tasklist' (for a specific task list) or 'list-tasks' (for tasks within a list). The description implies a broad retrieval but offers no context about prerequisites, filtering, or use cases.

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/arpitbatra123/mcp-googletasks'

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