Skip to main content
Glama
Sign In
ClickUp MCP Server

ClickUp MCP Server

by azukhrufy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_time_entries

Retrieve tracked time entries from ClickUp team workspaces. Filter by task, list, space, folder, assignee, or date range to get specific time logs.

Instructions

Get tracked time entries for a ClickUp team/workspace.

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": {
      "team_id": "<team_id>"
    },
    "name": "get_time_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
list_idNoFilter by list ID
task_idNoFilter by task ID
team_idYesThe ID of the team (workspace)
assigneeNoFilter by assignee user ID
end_dateNoEnd date as ms timestamp
space_idNoFilter by space ID
folder_idNoFilter by folder ID
start_dateNoStart date as ms timestamp

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only restates the get operation and adds the team/workspace scope. It does not mention response format, pagination, or how filters behave, leaving significant ambiguity.

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 a single sentence 'Get tracked time entries for a ClickUp team/workspace' that is front-loaded, clear, and contains no filler, making it highly concise.

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?

For a tool with 8 parameters and no output schema or annotations, this one-line description is insufficient. It does not explain what a 'tracked time entry' is, how filters combine, or what the response contains, leaving the agent without enough context for correct invocation.

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?

All 8 parameters have descriptions in the schema (100% coverage), so the description is not required to explain parameter syntax. However, it adds no extra meaning about parameter interplay or the importance of team_id, so it stays at the baseline.

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 uses a specific verb 'Get' with a clear resource 'tracked time entries' and scope 'for a ClickUp team/workspace', distinguishing it from sibling tools like create_time_entry and delete_time_entry.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool versus alternatives like get_team_tasks or get_tasks, and provides no exclusions or prerequisites beyond the obvious team/workspace scope.

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