Skip to main content
Glama
Sign In
ClickUp MCP Server

ClickUp MCP Server

by ttttdiva
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_folder_lists

Get all lists within a specific ClickUp folder by providing the folder ID.

Instructions

フォルダー内のリスト一覧を取得します。

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": {
      "folder_id": "<folder_id>"
    },
    "name": "get_folder_lists"
  }
}

Input Schema

NameRequiredDescriptionDefault
folder_idYesフォルダーID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the basic retrieval action without mentioning return format, pagination, or potential side effects, adding no value beyond the name.

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, concise sentence with no superfluous content. It front-loads the essential action and scope, making it easy to parse.

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

Completeness3/5

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

Although the tool is simple and the description states its core function, the presence of sibling tools like get_lists creates potential ambiguity about when this tool should be used. The description does not address this or mention return structure, leaving a moderate gap in completeness.

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 schema fully describes the single parameter folder_id with a clear description, covering 100% of the parameters. The description does not add any additional context, so the baseline score of 3 is appropriate.

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 retrieves a list of lists within a folder (フォルダー内のリスト一覧), using the specific verb 取得. This distinguishes it from siblings like get_lists and get_folders by explicitly scoping to a folder.

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?

No guidance is provided on when to use this tool versus alternatives such as get_lists or get_folders. The description implies usage when a folder_id is available, but it does not explicitly state exclusions, prerequisites, or mention alternative tools.

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