Skip to main content
Glama

bulk_delete_tasks

Delete multiple tasks from a calendar by specifying the calendar UID and a list of task UIDs.

Instructions

Delete multiple tasks in bulk

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoOperation modecontinue
accountNoAccount alias
parallelNoExecute operations in parallel
task_uidsYesList of task UIDs to delete
request_idNo
calendar_uidYesCalendar UID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

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 fails to state whether deletions are permanent, handle partial failures, or mention any rate limits or permissions, leaving significant gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence with no wasted words. However, it could be slightly expanded to include more context without being verbose.

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?

Despite having an output schema (not shown), the description lacks crucial context like the behavior of mode and parallel parameters, reversibility, and prerequisites. For a bulk operation, this is insufficient.

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 high (83%), so the schema already documents most parameters. The description adds no extra meaning beyond the schema. Baseline of 3 is appropriate.

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

Purpose5/5

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

The description 'Delete multiple tasks in bulk' clearly states the verb (Delete), resource (tasks), and scope (multiple). It distinguishes from sibling tools like delete_task (single) and other bulk_delete_* tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for deleting multiple tasks but provides no explicit when-to-use or when-not-to-use guidance. No alternatives or exclusions are mentioned, though sibling tool names help differentiate.

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/democratize-technology/chronos-mcp'

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