Skip to main content
Glama

add_project

Create a new project in Things.app with notes, tags, area assignment, and initial to-dos. Schedule start dates, set deadlines, and mark as completed or canceled. Supports markdown notes and date overrides for historical imports.

Instructions

Create a new project in Things.app. Add notes, tags, assign to areas, and pre-populate with initial to-dos.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesProject title (required). Clear name describing the project goal, outcome, or deliverable
notesNoProject description, objectives, scope, or additional context (max 10,000 characters). Supports markdown formatting for rich text documentation
whenNoSchedule when to start working on this project. Use "today" to start immediately, "tomorrow" to start next day, "evening" to start later today, "anytime" for flexible timing, "someday" for future consideration, or ISO date format (YYYY-MM-DD) for specific start date
deadlineNoSet a deadline for project completion in ISO date format (YYYY-MM-DD). Creates deadline tracking and reminders in Things.app
tagsNoArray of tag names for categorizing and organizing the project (max 20 tags). Tags help with filtering and project management
areaIdNoID of the area of responsibility to assign this project to. Use this when you know the specific area ID
areaNameNoName of the area of responsibility to assign this project to (e.g., "Work", "Personal", "Health", "Finance"). Areas help organize projects by life domain
initialTodosNoArray of initial to-do item descriptions to create within the project (max 50 items). Each string becomes a separate task within the project
completedNoMark the project as completed immediately upon creation (default: false). Useful for logging already completed projects
canceledNoMark the project as canceled immediately upon creation (default: false). Useful for recording projects that are no longer viable
creationDateNoOverride the creation date with a specific ISO8601 datetime (YYYY-MM-DDTHH:MM:SS). Useful for importing historical project data
completionDateNoSet a specific completion date using ISO8601 datetime (YYYY-MM-DDTHH:MM:SS). Only used when completed is true
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It describes the creation behavior and supported fields but omits details on error handling, return value, idempotency, or permissions.

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?

The description is two sentences, front-loaded with the core action, and no extraneous words. It efficiently conveys the purpose and key features.

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

Completeness3/5

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

Given 12 parameters fully described in the schema and no output schema, the description is adequate but incomplete. It does not mention what the tool returns (e.g., project ID) or handle error conditions, which are important for an AI agent.

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 100% with detailed parameter descriptions in the input schema. The tool description only provides a high-level summary of capabilities (notes, tags, areas, todos) without adding meaning beyond what the schema already provides.

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 action ('Create a new project') and the resource ('in Things.app'), and lists specific capabilities (notes, tags, areas, initial to-dos) that distinguish it from sibling tools like add_todo.

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?

The description implies usage for project creation but does not explicitly state when to use this tool versus alternatives like add_todo or update_project. No exclusions or alternative recommendations are provided.

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

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