Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_get_task_time_in_status

Read-onlyIdempotent

Retrieve the amount of time a task has spent in each status. Use for cycle-time and workflow analysis on individual tasks.

Instructions

Report how long one task has spent in each status.

Calls GET /task/{task_id}/time_in_status. Requires the 'Total time in Status' ClickApp to be enabled. Set custom_task_ids=true (+ team_id) to address the task by Custom Task ID.

When to Use:

  • Cycle-time / workflow analysis for a single task.

When NOT to Use:

  • For many tasks at once — use clickup_get_bulk_tasks_time_in_status.

Returns: Markdown (current status + per-status history in Xh Ym) or raw JSON.

Examples:

  • params = {"task_id": "86cxy1"}

Error Handling: An empty result usually means the ClickApp is disabled; 404 means a bad id.

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?

Annotations already indicate read-only and idempotent behavior. The description adds critical context: the prerequisite ClickApp, return format (Markdown/JSON), and error conditions (empty result vs 404). No contradictions.

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 well-structured with clear sections (usage, returns, examples, errors). Every sentence adds value, and the information is front-loaded.

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?

Given the tool's simplicity, the description covers all aspects: purpose, prerequisites, usage boundaries, parameter hints, example, error handling, and return format. Output schema exists, so return values need not be detailed.

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?

Although schema coverage is 0%, the description supplements parameter meaning by explaining the interplay of custom_task_ids and team_id, and mentions response_format indirectly. Schema descriptions also exist for each parameter.

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 clearly states the tool's purpose: 'Report how long one task has spent in each status.' It specifies the API endpoint and distinguishes itself from the sibling tool 'clickup_get_bulk_tasks_time_in_status', making its scope unmistakable.

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 are provided, along with a concrete alternative tool. Examples and error handling further guide usage.

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