Skip to main content
Glama
evalor
by evalor

Update Project

update_project

Update an existing project's settings: rename, change color, view mode, type, or reorder. Only provide fields to change.

Instructions

Update an existing project's (清单) settings.

WHEN TO USE:

  • Rename a project (重命名清单)

  • Change project color (颜色), view mode (视图模式), or type (类型)

  • Reorder projects in the list (调整清单顺序)

PARTIAL UPDATE: Only provide fields you want to change. Unspecified fields remain unchanged.

REQUIRED: projectId (清单ID)

OPTIONAL (at least one required):

  • name: New project name (新名称)

  • color: New hex color (新颜色, e.g., '#F18181')

  • viewMode: 'list' (列表), 'kanban' (看板), or 'timeline' (时间线)

  • kind: 'TASK' (任务清单) or 'NOTE' (笔记清单)

  • sortOrder: New position in project list (新排序位置)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoNew project type (新类型): 'TASK' (任务清单), 'NOTE' (笔记清单). Optional.
nameNoNew project name (新清单名称). Optional.
colorNoNew project color in hex format (新颜色, e.g., '#F18181'). Optional.
viewModeNoNew view mode (新视图模式): 'list' (列表), 'kanban' (看板), 'timeline' (时间线). Optional.
projectIdYesThe unique ID of the project to update (清单ID, required)
sortOrderNoNew sort order (新排序位置). Optional.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
kindNo
nameYes
colorNo
closedNo
groupIdNo
viewModeNo
sortOrderNo
permissionNo
Behavior4/5

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

No annotations exist, so the description carries full burden. It discloses partial update behavior, required projectId, and optional parameters. It does not cover permissions, reversibility, or potential side effects, but for a simple update tool this is sufficient.

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?

Description is well-structured with headings and bullet points, each section concise and valuable. No redundant information; front-loaded with purpose and usage.

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?

Given the tool's complexity (6 parameters, 1 required) and 100% schema coverage, the description is complete. It covers usage, partial update, and parameter details. Output schema exists but its content is not needed for completeness.

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

Parameters4/5

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

Schema coverage is 100%, but the description adds meaning by grouping fields (required/optional), providing Chinese translations, and clarifying the 'at least one required' constraint. Examples for color and sortOrder further aid 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 'Update an existing project's settings' and lists specific use cases (rename, change color, view mode, type, reorder). It distinguishes from siblings like create_project and delete_project through context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description includes a 'WHEN TO USE' section with explicit scenarios, partial update behavior, and required vs optional parameters. It does not explicitly state when NOT to use it or mention alternatives like create_project, but the sibling list and context signals provide implicit differentiation.

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/evalor/Dida365MCP'

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