Skip to main content
Glama
mstfe

Google Tasks MCP Server

by mstfe

delete_task

Remove a task from your Google Tasks default list by specifying its ID to manage and organize your tasks effectively.

Instructions

Delete a task from the default task list

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskIdYesID of the task to delete

Implementation Reference

  • Handler for the 'delete_task' tool. Validates arguments (using create_task validator, note potential bug), extracts taskId, calls Google Tasks API to delete the task, returns success message or throws error.
    if (request.params.name === "delete_task") {
      if (!isValidCreateTaskArgs(request.params.arguments)) {
        throw new McpError(
          ErrorCode.InvalidParams,
          "Invalid arguments for creating a task. 'title' must be a string, and 'notes' must be a string or undefined."
        );
      }
      const args = request.params.arguments;
      const taskId  = args.taskId;
      if (!taskId) {
        throw new McpError(
          ErrorCode.InvalidParams,
          "The 'taskId' field is required."
        );
      }
      try {
        await tasks.tasks.delete({
          tasklist: "@default",
          task: taskId,
        });
    
        return {
          content: [
            {
              type: "text",
              text: "Task deleted successfully.",
            },
          ],
        };
      } catch (error) {
        throw new McpError(
          ErrorCode.InternalError,
          `Tasks API error: ${error}`
        );
      }
    }
  • src/index.ts:162-172 (registration)
    Registration of the 'delete_task' tool in the ListTools response, including name, description, and input schema.
    {
      name: "delete_task",
      description: "Delete a task from the default task list",
      inputSchema: {
        type: "object",
        properties: {
          taskId: { type: "string", description: "ID of the task to delete" },
        },
        required: ["taskId"],
      },
    },
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 this is a deletion operation, implying it's destructive, but doesn't clarify if deletions are permanent/reversible, what permissions are required, or what happens on success/failure. For a mutation tool with zero annotation coverage, this is insufficient.

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 front-loads the core action ('Delete a task') without any wasted words. It's appropriately sized for a simple tool with one parameter.

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 mutation tool with no annotations and no output schema, the description is incomplete. It doesn't address critical context like what 'delete' entails (permanent removal?), error conditions, or return values, leaving significant gaps for agent understanding.

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?

The input schema has 100% description coverage, with the single parameter 'taskId' clearly documented. The description adds no additional parameter semantics beyond implying deletion targets a specific task ID, so it meets the baseline of 3 where the schema does the heavy lifting.

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 verb ('Delete') and resource ('a task from the default task list'), making the purpose immediately understandable. However, it doesn't explicitly distinguish this from sibling tools like 'complete_task' which might also remove tasks from view, though deletion is more permanent.

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 like 'complete_task' or 'list_tasks'. It doesn't mention prerequisites (e.g., needing an existing task ID) or warn against misuse, leaving the agent to infer usage from context 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/mstfe/mcp-google-tasks'

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