Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_get_list_views

Read-onlyIdempotent

Retrieve all views for a specific ClickUp List, including custom and built-in views, to get their IDs before accessing view details or tasks.

Instructions

List the task and page views available for a List.

ClickUp returns custom views and the List's built-in ("required") views — e.g. the default List view — as separate arrays; both are shown here.

When to Use:

  • Discovering existing List-level views (and their ids) before calling clickup_get_view, clickup_get_view_tasks, or clickup_update_view.

When NOT to Use:

  • Everything-, Space-, or Folder-level views — use clickup_get_team_views / clickup_get_space_views / clickup_get_folder_views.

Returns: Markdown (default) or JSON listing of views: id, name, type, parent, plus any built-in required_views.

Examples: params = {"list_id": "901"}

Error Handling: 404 means the List id is wrong.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint; the description adds meaningful context about return structure (separate arrays for custom and built-in views), error handling, and output format, without contradiction.

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?

Well-structured with clear sections (main description, when to use, when not, returns, examples, error handling). Every sentence adds value without redundancy.

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

Completeness5/5

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

The description fully covers the tool's purpose, usage context, return behavior, and error scenarios. The presence of an output schema further reduces the need to explain return values.

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?

Despite 0% schema description coverage per context, the description provides an example with 'list_id' and implies the 'response_format' parameter by mentioning return formats. However, it does not explicitly describe the parameters beyond that, leaving some burden unaddressed.

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 lists task and page views for a List, with a specific verb and resource. It distinguishes from sibling tools like 'clickup_get_team_views' by specifying it's for List-level views.

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 provides when to use (discovering List-level views before related operations) and when NOT to use (other levels refer to specific sibling tools), with direct mentions of alternatives.

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/trustxai/clickup-mcp'

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