MCP Time Tracking Tools Broken — `tags` Schema Mismatch
abenger
Both
clickup_get_time_entries
and clickup_get_task_time_entries
are broken due to a tags
field type mismatch in the output schema.Root Cause:
The ClickUp API returns
tags
as an array of objects ([{name, tag_fg, tag_bg, ...}]
), but the MCP output schema defines it as string[]
. This fails structured content validation.Symptoms:
- get_time_entries: Throws MCP error-32602with"expected": "string", "received": "object"for every entry. In our test, the API successfully returned 206 entries but all were rejected by validation.
- get_task_time_entries: Silently returns empty results ({"timeEntries": [], "total": 0}) on tasks that have confirmed tracked time viaget_task(time_spent > 0). Verified across multiple tasks.
Fix:
Update the output schema for both tools to define
tags
as an array of objects.Note:
These tools were working via Claude.ai in mid-March 2026.
This may also explain Gretchen Elliott's March 17 report in this thread —
get_time_entries
does exist as an MCP tool but is currently unusable.Log In