Skip to main content
Glama
arpitbatra123

Google Tasks MCP Server

delete-task

Remove a specific task from a Google Tasks list by providing the task list ID and task ID.

Instructions

Delete a task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tasklistYesTask list ID
taskYesTask ID to delete

Implementation Reference

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

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Delete a task' implies a destructive mutation, but it doesn't specify whether deletion is permanent or reversible, what permissions are required, whether there are confirmation prompts, or what happens to associated data. For a destructive operation with zero annotation coverage, this is inadequate behavioral transparency.

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 maximally concise with just three words that directly state the tool's function. There's no wasted language or unnecessary elaboration. While it's arguably too brief for a destructive operation, from a pure conciseness perspective, it's perfectly efficient.

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?

For a destructive mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't address critical context like authentication requirements, error conditions, what constitutes successful deletion, or how this differs from related deletion operations. The agent would need to guess about many behavioral aspects when invoking this tool.

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 both parameters ('tasklist' and 'task') clearly documented in the schema. The description adds no additional parameter information beyond what's already in the structured schema. According to the scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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' clearly states the action (delete) and resource (task), which is better than a tautology. However, it doesn't distinguish this tool from sibling tools like 'delete-tasklist' or 'clear-completed-tasks' that also perform deletion operations on related resources. The purpose is understandable but lacks specificity about what kind of task deletion this performs.

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. It doesn't mention prerequisites (like authentication), when deletion is appropriate versus other operations like 'complete-task' or 'update-task', or what happens after deletion. With multiple sibling tools available, this lack of context leaves the agent guessing about appropriate usage scenarios.

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