Skip to main content
Glama
Sign In
tick-mcp

tick-mcp

by KpihX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

batch_delete_tasks

Batch delete multiple tasks by providing a list of task and project IDs.

Instructions

Delete multiple tasks at once via V2 batch.

[Category: Tasks — Batch]  [Auth: V2]
[Related: delete_task, batch_create_tasks]

Args:
    tasks: List of {"taskId": "...", "projectId": "..."}.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tasks": "<tasks>"
    },
    "name": "batch_delete_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
tasksYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
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. It mentions V2 batch but omits important behavioral details such as error handling, atomicity, rate limits, or partial success behavior in a batch delete operation.

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 concise, with a short main sentence, a structured metadata line (Category, Auth, Related), and a clear args section. Every sentence adds value without redundancy.

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

Completeness3/5

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

The description lacks details about return values or error behavior, which is important for a batch operation. With no output schema and no annotations, it leaves gaps despite covering the basic purpose and parameters.

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% coverage and defines tasks as an array with additionalProperties: true, which is vague. The description compensates by specifying the required structure: each item must have 'taskId' and 'projectId', which is essential for correct tool invocation.

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 explicitly states 'Delete multiple tasks at once via V2 batch', which is a specific verb and resource. It distinguishes from sibling tools like delete_task (individual) and batch_create_tasks (creation).

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

Usage Guidelines4/5

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

The description lists related tools (delete_task, batch_create_tasks), offering context for alternatives. However, it does not explicitly state when to use this tool vs others or provide exclusion criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools