Skip to main content
Glama
arpitbatra123

Google Tasks MCP Server

delete-tasklist

Remove a task list from Google Tasks by specifying its ID, helping users manage their task organization by eliminating unwanted lists.

Instructions

Delete a task list

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tasklistYesTask list ID to delete

Implementation Reference

  • Handler function for 'delete-tasklist' tool: authenticates user, calls Google Tasks API to delete the specified tasklist, returns success or error message.
    async ({ tasklist }) => {
      if (!isAuthenticated()) {
        return {
          isError: true,
          content: [
            {
              type: "text",
              text: "Not authenticated. Please use the 'authenticate' tool first.",
            },
          ],
        };
      }
    
      try {
        await tasks.tasklists.delete({
          tasklist,
        });
    
        return {
          content: [
            {
              type: "text",
              text: `Task list with ID '${tasklist}' was successfully deleted.`,
            },
          ],
        };
      } catch (error) {
        console.error("Error deleting task list:", error);
        return {
          isError: true,
          content: [
            {
              type: "text",
              text: `Error deleting task list: ${error}`,
            },
          ],
        };
      }
    }
  • Zod input schema defining the 'tasklist' parameter as a required string.
    {
      tasklist: z.string().describe("Task list ID to delete"),
    },
  • src/index.ts:403-448 (registration)
    MCP server registration of the 'delete-tasklist' tool including name, description, schema, and inline handler.
    server.tool(
      "delete-tasklist",
      "Delete a task list",
      {
        tasklist: z.string().describe("Task list ID to delete"),
      },
      async ({ tasklist }) => {
        if (!isAuthenticated()) {
          return {
            isError: true,
            content: [
              {
                type: "text",
                text: "Not authenticated. Please use the 'authenticate' tool first.",
              },
            ],
          };
        }
    
        try {
          await tasks.tasklists.delete({
            tasklist,
          });
    
          return {
            content: [
              {
                type: "text",
                text: `Task list with ID '${tasklist}' was successfully deleted.`,
              },
            ],
          };
        } catch (error) {
          console.error("Error deleting task list:", error);
          return {
            isError: true,
            content: [
              {
                type: "text",
                text: `Error deleting task list: ${error}`,
              },
            ],
          };
        }
      }
    );
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action ('Delete a task list'). It doesn't disclose critical behavioral traits: whether deletion is permanent or reversible, what permissions are required, if it cascades to delete associated tasks, error conditions, or response format. This is inadequate for a destructive operation with zero annotation coverage.

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's appropriately sized for a simple tool and front-loaded with the core action. No unnecessary words or structural issues are present.

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 this is a destructive operation with no annotations and no output schema, the description is incomplete. It doesn't address safety concerns, return values, error handling, or how it differs from sibling tools. For a delete operation in a task management context, more context is needed to ensure correct usage.

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%, with the single parameter 'tasklist' documented as 'Task list ID to delete'. The description adds no additional meaning beyond this, as it doesn't explain parameter format, sourcing, or constraints. Baseline 3 is appropriate since the schema fully describes the parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Delete a task list' clearly states the action (delete) and resource (task list), but it's vague about scope and doesn't distinguish from sibling tools like 'delete-task' or 'clear-completed-tasks'. It provides basic purpose but lacks specificity about what constitutes a task list deletion versus other deletion 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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing an existing task list ID), exclusions, or comparisons to siblings like 'delete-task' or 'clear-completed-tasks'. Users must infer usage from the name alone.

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