Skip to main content
Glama
Sign In
ClickUp MCP Server

ClickUp MCP Server

by ttttdiva
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search_tasks

Search tasks in ClickUp by query, tags, status, assignees, or date range. Filter out closed tasks or those without start dates.

Instructions

タスクを検索します。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoタグでフィルタ
queryNo検索クエリ
team_idNoチームID（省略時は環境変数のTEAM_IDを使用）
statusesNoステータスでフィルタ
assigneesNo担当者でフィルタ
start_date_gtNo開始日がこの日付より後のタスクを検索 (YYYY-MM-DD)
start_date_ltNo開始日がこの日付より前のタスクを検索 (YYYY-MM-DD)
exclude_closedNoClosedステータスのタスクを除外する
exclude_no_start_dateNo開始日が未設定のタスクを除外する

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.9/5.0
Behavior1/5

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states that it searches tasks. It does not disclose return format, pagination, read-only nature, rate limits, or how filters interact. This provides zero transparency about the tool's runtime behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence, but it is under-specified rather than concise. It earns no place because it provides no information beyond the tool name. A concise description should pack essential usage details; this one is merely abbreviated to the point of being unhelpful.

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

Completeness1/5

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

This is a 9-parameter tool with no output schema, yet the description is a single vague sentence. It gives no overview of the search capabilities, the meaning of filters, or the returned data. The description is wholly inadequate for an agent to understand when and how to correctly invoke this tool.

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?

The input schema covers 100% of the 9 parameters with clear Japanese descriptions, so the baseline is 3. The description adds no parameter context, such as whether multiple tags/statuses are OR or AND filters or the exclusivity of date range bounds. However, the schema is self-explanatory, so the lack of description is not a major penalty.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'タスクを検索します。' (Search tasks) merely restates the tool name 'search_tasks' without adding scope or distinguishing from sibling tools like get_tasks or get_task_detail. It is a tautology that fails to convey what makes this search tool unique, such as the rich set of filters it supports.

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 provides no usage guidance whatsoever. It does not indicate when to use search_tasks versus alternatives like get_tasks, nor does it mention any context, prerequisites, or exclusions. An agent is left without any direction on when to select this tool over its siblings.

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