Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_get_bulk_tasks_time_in_status

Read-onlyIdempotent

Fetch time-in-status for 2 to 100 tasks in a single call to analyze cycle time across a batch of tasks.

Instructions

Report time-in-status for 2 to 100 tasks in one call.

Calls GET /task/bulk_time_in_status/task_ids with each id passed as a repeated task_ids query param. Requires the 'Total time in Status' ClickApp. Set custom_task_ids=true (+ team_id) to address tasks by Custom Task ID.

When to Use:

  • Cycle-time analysis across a batch of tasks.

When NOT to Use:

  • For a single task, clickup_get_task_time_in_status is simpler — ClickUp's bulk endpoint requires at least 2 task ids.

Returns: Markdown grouped per task (current status + history), or raw JSON keyed by task id.

Examples:

  • params = {"task_ids": ["86a", "86b", "86c"]}

Error Handling: Fewer than 2 or more than 100 ids is rejected client-side; empty results mean the ClickApp is disabled.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Adds details beyond annotations: requires 'Total time in Status' ClickApp, explains error handling (client-side rejection, empty results meaning disabled app), and describes return format choices.

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?

Well-organized with sections, no wasted words, every sentence provides essential information.

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

Completeness5/5

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

Covers purpose, usage boundaries, prerequisites, error handling, return format, and example. Fully sufficient given the tool's complexity and existing annotations/output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Description adds context to schema parameters: explains API call structure (repeated query param), how to use custom_task_ids with team_id, and provides an example. Schema descriptions are already detailed, so additional value is present.

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?

Description clearly states 'Report time-in-status for 2 to 100 tasks in one call.' and distinguishes from the sibling single-task tool by name and use case.

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

Usage Guidelines5/5

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

Explicit 'When to Use' and 'When NOT to Use' sections, including the specific alternative tool name and the minimum count requirement.

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/trustxai/clickup-mcp'

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