Skip to main content
Glama

update-project

Update existing projects in Things by modifying titles, notes, tags, schedules, deadlines, areas, and completion status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the project to update (required)
areaNoTitle of area to move to
tagsNoReplace all current tags
whenNoWhen to schedule (cannot update repeating projects)
notesNoNew notes (replaces existing, max 10,000 chars)
titleNoNew title (replaces existing)
revealNoNavigate to and show the updated project
area-idNoID of area to move to
add-tagsNoAdd these tags to existing ones
canceledNoMark as canceled/incomplete
deadlineNoDeadline date (cannot update repeating projects)
completedNoMark as completed/incomplete
duplicateNoDuplicate before updating
auth-tokenYesThings URL scheme authorization token (required)
append-notesNoText to add after existing notes
creation-dateNoISO8601 date time string for creation date
prepend-notesNoText to add before existing notes
completion-dateNoISO8601 date time string for completion date
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/jimfilippou/things-mcp'

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