Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_create_team_view

Create a Workspace-level view containing tasks from every Space, useful for cross-Space dashboards and applying custom fields to all tasks.

Instructions

Create a task or page view at the Everything Level of a Workspace.

Everything-Level views can surface tasks from every Space in the Workspace, which makes this the level to use for cross-Space dashboards.

When to Use:

  • Building a Workspace-wide view (e.g. a Board across every Space).

  • The view needs Custom Field columns that should apply to every task in the Workspace — see the columns field note.

When NOT to Use:

  • The view only needs tasks from one Space/Folder/List — use clickup_create_space_view / clickup_create_folder_view / clickup_create_list_view, which scope the view naturally.

Returns: A confirmation string with the new view's id, name, and type, or an Error ... string.

Examples: params = { "team_id": "123", "name": "Everything Board", "type": "board", "grouping": {"field": "status"}, }

Error Handling: 404 means the Workspace (team) id is wrong; 403 can mean the token lacks access to this Workspace.

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?

Beyond annotations, the description discloses important behaviors: Custom Fields added at this level apply to every task and prevent moving the view, error handling for 404/403, and confirmation string return format.

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 (purpose, when to use/not use, 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 is comprehensive for the tool's complexity: it covers purpose, usage boundaries, parameter nuances, return type, and error scenarios, leaving no critical gaps for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds meaningful context to parameters, especially the 'columns' field with its permanent effect, and provides an example usage. Schema descriptions are also present, but the description enhances understanding.

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 the tool creates a view at the Everything Level of a Workspace, distinguishing it from other view creation tools by explaining the cross-Space scope and when to use alternatives.

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?

Explicit 'When to Use' and 'When NOT to Use' sections provide clear guidance, naming specific sibling tools (clickup_create_space_view, clickup_create_folder_view, clickup_create_list_view) for different contexts.

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