Skip to main content
Glama

update_project

Rename or change the color, view mode, kind, or sort order of an existing TickTick project to keep its settings aligned with your workflow.

Instructions

Rename or change the color, view or kind of an existing TickTick project.

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": {
      "projectId": "<projectId>"
    },
    "name": "update_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
nameNo
colorNo
viewModeNo
projectIdYesTickTick project ID.
sortOrderNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is covered. The description adds which attributes are mutable, but never says whether this is a partial update (fields omitted left unchanged) or a full overwrite, nor what renaming does to references elsewhere. That partial-vs-full question is the main behavioral gap for a mutation tool with 6 params.

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

Conciseness4/5

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

A single front-loaded sentence with no filler, and the resource is stated up front before the mutable fields. Its brevity is close to the lower bound for a six-parameter tool, but nothing in the text is wasted.

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

Completeness2/5

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

For a mutation with six parameters, 17% schema coverage, no output schema and no annotation detail beyond non-destructive, the definition leaves out sortOrder entirely and does not clarify update semantics or the response. An agent could call it but would be guessing about ordering and partial-update behavior.

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?

Schema coverage is only 17% (only projectId is described), so the description must compensate. It names four of the six parameters (name, color, viewMode, kind) in natural language, which helps, but sortOrder is never mentioned and neither enum's allowed values or semantics are explained.

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

Purpose4/5

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

Uses a specific verb set (rename, change color/view/kind) against a specific resource (an existing TickTick project), which cleanly separates it from create_project, delete_project and get_project. It does not name sibling tools explicitly, but the 'existing project' framing makes the mutation scope unambiguous.

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

Usage Guidelines3/5

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

Implies usage by saying 'existing ... project', which tells the agent a project must already exist, but gives no explicit when-to-use versus create_project, no prerequisites (can you change kind on a project with tasks?), and no exclusions. Guidance is inferred rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.