Skip to main content
Glama

clickup_task_search

Search tasks across your ClickUp workspace using filters like assignee, status, tags, dates, custom fields, and more. Returns a paginated list of matching tasks.

Instructions

Search tasks across an entire ClickUp workspace with ClickUp's filtered team tasks endpoint. Supports hierarchy, assignee, status, tag, date range, custom field, custom item type, parent/subtask, and ordering filters. Returns a paginated array of task objects. For tasks in a single list, prefer clickup_task_list (fewer parameters, same shape).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assigneesNoUser IDs (as strings) to restrict to tasks assigned to them. Obtain from clickup_member_list. Omit to return tasks regardless of assignee.
custom_fieldsNoClickUp custom field filters. Each object is sent inside the custom_fields JSON query parameter, e.g. [{"field_id":"...","operator":"=","value":"..."}]. Use operators supported by ClickUp, including IS NULL / IS NOT NULL for unset/set checks.
custom_itemsNoFilter by ClickUp custom task type IDs. Include 0 for regular tasks, 1 for milestones, or workspace-defined custom item type IDs.
date_created_gtNoFilter tasks created after this Unix timestamp in milliseconds.
date_created_ltNoFilter tasks created before this Unix timestamp in milliseconds.
date_done_gtNoFilter tasks completed after this Unix timestamp in milliseconds.
date_done_ltNoFilter tasks completed before this Unix timestamp in milliseconds.
date_updated_gtNoFilter tasks updated after this Unix timestamp in milliseconds.
date_updated_ltNoFilter tasks updated before this Unix timestamp in milliseconds.
due_date_gtNoFilter tasks with due_date greater than this Unix timestamp in milliseconds.
due_date_ltNoFilter tasks with due_date less than this Unix timestamp in milliseconds.
include_closedNotrue = include tasks in closed statuses; false or omitted = exclude closed tasks.
include_markdown_descriptionNotrue = ask ClickUp to return task descriptions in Markdown format.
list_idsNoRestrict results to these list IDs. Obtain from clickup_list_list (field: id). Omit to search all lists.
order_byNoSort field supported by ClickUp, such as id, created, updated, or due_date.
parentNoParent task ID. When set, returns subtasks under this parent task.
project_idsNoRestrict results to these folder/project IDs. ClickUp's API parameter is project_ids[]. Obtain IDs from clickup_folder_list.
reverseNotrue = reverse the selected sort order.
space_idsNoRestrict results to these space IDs. Obtain from clickup_space_list (field: id). Omit to search all spaces.
statusesNoStatus names to include (e.g. ['open','in review']). Case-sensitive. Omit for any open status.
subtasksNotrue = include subtasks in search results; false or omitted = exclude subtasks unless parent is provided.
tagsNoTag names to filter by. Tags must match ClickUp tag names in the relevant spaces.
team_idNoWorkspace (team) ID to search within. Obtain from clickup_workspace_list (field: id). Omit to use the default workspace from config.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed18 schema fields changedv0.10.0
    • addedInput schema / properties / custom_fields
      Added value: +{
      +  "description": "ClickUp custom field filters. Each object is sent inside the custom_fields JSON query parameter, e.g. [{\"field_id\":\"...\",\"operator\":\"=\",\"value\":\"...\"}]. Use operators supported by ClickUp, including IS NULL / IS NOT NULL for unset/set checks.",
      +  "items": {
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / custom_items
      Added value: +{
      +  "description": "Filter by ClickUp custom task type IDs. Include 0 for regular tasks, 1 for milestones, or workspace-defined custom item type IDs.",
      +  "items": {
      +    "type": "integer"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / date_created_gt
      Added value: +{
      +  "description": "Filter tasks created after this Unix timestamp in milliseconds.",
      +  "type": "integer"
      +}
    • addedInput schema / properties / date_created_lt
      Added value: +{
      +  "description": "Filter tasks created before this Unix timestamp in milliseconds.",
      +  "type": "integer"
      +}
    • addedInput schema / properties / date_done_gt
      Added value: +{
      +  "description": "Filter tasks completed after this Unix timestamp in milliseconds.",
      +  "type": "integer"
      +}
    • addedInput schema / properties / date_done_lt
      Added value: +{
      +  "description": "Filter tasks completed before this Unix timestamp in milliseconds.",
      +  "type": "integer"
      +}
    • addedInput schema / properties / date_updated_gt
      Added value: +{
      +  "description": "Filter tasks updated after this Unix timestamp in milliseconds.",
      +  "type": "integer"
      +}
    • addedInput schema / properties / date_updated_lt
      Added value: +{
      +  "description": "Filter tasks updated before this Unix timestamp in milliseconds.",
      +  "type": "integer"
      +}
    • addedInput schema / properties / due_date_gt
      Added value: +{
      +  "description": "Filter tasks with due_date greater than this Unix timestamp in milliseconds.",
      +  "type": "integer"
      +}
    • addedInput schema / properties / due_date_lt
      Added value: +{
      +  "description": "Filter tasks with due_date less than this Unix timestamp in milliseconds.",
      +  "type": "integer"
      +}
    • addedInput schema / properties / include_closed
      Added value: +{
      +  "description": "true = include tasks in closed statuses; false or omitted = exclude closed tasks.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / include_markdown_description
      Added value: +{
      +  "description": "true = ask ClickUp to return task descriptions in Markdown format.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / order_by
      Added value: +{
      +  "description": "Sort field supported by ClickUp, such as id, created, updated, or due_date.",
      +  "type": "string"
      +}
    • addedInput schema / properties / parent
      Added value: +{
      +  "description": "Parent task ID. When set, returns subtasks under this parent task.",
      +  "type": "string"
      +}
    • addedInput schema / properties / project_ids
      Added value: +{
      +  "description": "Restrict results to these folder/project IDs. ClickUp's API parameter is project_ids[]. Obtain IDs from clickup_folder_list.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / reverse
      Added value: +{
      +  "description": "true = reverse the selected sort order.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / subtasks
      Added value: +{
      +  "description": "true = include subtasks in search results; false or omitted = exclude subtasks unless parent is provided.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / tags
      Added value: +{
      +  "description": "Tag names to filter by. Tags must match ClickUp tag names in the relevant spaces.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  2. Changed5 schema fields changedv0.1.1
    • changedInput schema / properties / assignees / description
      Previous value: -"Filter by assignee user IDs"New value: +"User IDs (as strings) to restrict to tasks assigned to them. Obtain from clickup_member_list. Omit to return tasks regardless of assignee."
    • changedInput schema / properties / list_ids / description
      Previous value: -"Filter by list IDs"New value: +"Restrict results to these list IDs. Obtain from clickup_list_list (field: id). Omit to search all lists."
    • changedInput schema / properties / space_ids / description
      Previous value: -"Filter by space IDs"New value: +"Restrict results to these space IDs. Obtain from clickup_space_list (field: id). Omit to search all spaces."
    • changedInput schema / properties / statuses / description
      Previous value: -"Filter by status names"New value: +"Status names to include (e.g. ['open','in review']). Case-sensitive. Omit for any open status."
    • changedInput schema / properties / team_id / description
      Previous value: -"Workspace (team) ID. Omit to use the default workspace from config."New value: +"Workspace (team) ID to search within. Obtain from clickup_workspace_list (field: id). Omit to use the default workspace from config."
  3. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description fully discloses behavior: it returns a paginated array of task objects and supports many filters. It does not mention rate limits or permissions, but as a read/search tool, this is acceptable.

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, consisting of two sentences plus an alternative recommendation. It is front-loaded with the core purpose and efficiently covers the range of filters.

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

Completeness4/5

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

Given the complexity (23 parameters, no output schema), the description mentions pagination and key filter categories. It lacks details on pagination behavior but is otherwise sufficient for understanding the tool's capabilities.

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?

Schema coverage is 100% with detailed descriptions for each parameter. The tool description only summarizes the parameter types without adding new meaning beyond what the schema provides.

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 it searches tasks across an entire workspace using ClickUp's filtered team tasks endpoint, listing many filter types. It distinguishes itself from the sibling tool clickup_task_list by noting that the latter is for single-list tasks with fewer parameters.

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?

Explicitly advises to prefer clickup_task_list for tasks in a single list, providing a clear alternative. This helps an AI agent decide which tool to use based on the scope of the search.

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/nicholasbester/clickup-cli'

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