Skip to main content
Glama

update_project

Modify existing projects in Things.app by updating titles, notes, scheduling, tags, areas, and completion status to reflect changes in goals or progress.

Instructions

Update an existing project in Things.app. Modify title, notes, scheduling, tags, area assignment, and completion status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe unique ID of the project to update. This ID can be obtained from the list_projects tool
titleNoUpdate the project title with a new clear name describing the project goal, outcome, or deliverable
notesNoReplace existing notes with new project description, objectives, or context (max 10,000 characters). Supports markdown formatting. This completely replaces existing notes
prependNotesNoAdd text to the beginning of existing notes without replacing them. Useful for adding project updates or new objectives
appendNotesNoAdd text to the end of existing notes without replacing them. Useful for adding progress updates or new requirements
whenNoReschedule 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
deadlineNoUpdate the project deadline in ISO date format (YYYY-MM-DD). Creates or updates deadline tracking and reminders in Things.app
tagsNoReplace all current tags with this new set of tag names (max 20 tags). This completely replaces existing tags for the project
addTagsNoAdd these tag names to existing tags without removing current ones (max 20 total tags). Preserves existing project tags
areaIdNoMove the project to a different area of responsibility by specifying the area ID
areaNameNoMove the project to a different area of responsibility by specifying the area name (e.g., "Work", "Personal", "Health", "Finance")
completedNoMark the project as completed (true) or reopen it (false). Completed projects are moved to the Logbook along with all their to-dos
canceledNoMark the project as canceled (true) or restore it (false). Canceled projects are moved to the Trash along with all their to-dos
creationDateNoOverride the creation date with a specific ISO8601 datetime (YYYY-MM-DDTHH:MM:SS). Useful for data migration or historical project tracking
completionDateNoSet a specific completion date using ISO8601 datetime (YYYY-MM-DDTHH:MM:SS). Only used when marking the project as completed

Implementation Reference

  • The async handler function that implements the core logic of the 'update_project' tool. It handles authentication, completion/cancellation via JSON operations, and other updates via Things.app URL scheme.
    async (params) => {
      try {
        logger.info('Updating project', { id: params.id });
        
        const authToken = requireAuthToken();
        
        // Check if we're doing a completion/cancellation operation (use JSON)
        if (params.completed !== undefined || params.canceled !== undefined) {
          const attributes: Record<string, any> = {};
          
          if (params.completed !== undefined) {
            attributes.completed = params.completed;
            if (params.completionDate) {
              attributes['completion-date'] = params.completionDate;
            }
          }
          
          if (params.canceled !== undefined) {
            attributes.canceled = params.canceled;
          }
          
          const operation: JsonOperation = {
            type: 'project',
            operation: 'update',
            id: params.id,
            attributes
          };
          
          await executeJsonOperation(operation, authToken);
        } else {
          // Use URL scheme for other updates
          const urlParams: Record<string, any> = {
            id: params.id,
            'auth-token': authToken
          };
    
          // Map schema parameters to Things URL scheme parameters
          if (params.title) urlParams.title = params.title;
          if (params.notes) urlParams.notes = params.notes;
          if (params.prependNotes) urlParams['prepend-notes'] = params.prependNotes;
          if (params.appendNotes) urlParams['append-notes'] = params.appendNotes;
          if (params.when) urlParams.when = params.when;
          if (params.deadline) urlParams.deadline = params.deadline;
          if (params.tags) urlParams.tags = params.tags.join(',');
          if (params.addTags) urlParams['add-tags'] = params.addTags.join(',');
          if (params.areaId) urlParams['area-id'] = params.areaId;
          if (params.areaName) urlParams.area = params.areaName;
          if (params.creationDate) urlParams['creation-date'] = params.creationDate;
          
          const url = buildThingsUrl('update-project', urlParams);
          logger.debug('Generated URL', { url: url.replace(authToken, '***') });
          
          await openThingsUrl(url);
        }
        
        return {
          content: [{
            type: "text",
            text: `Successfully updated project: ${params.id}`
          }]
        };
      } catch (error) {
        logger.error('Failed to update project', { error: error instanceof Error ? error.message : error });
        throw error;
      }
    }
  • Zod schema defining all input parameters and validations for the 'update_project' tool.
    const updateProjectSchema = z.object({
      id: z.string().min(1).describe('The unique ID of the project to update. This ID can be obtained from the list_projects tool'),
      title: z.string().min(1).optional().describe('Update the project title with a new clear name describing the project goal, outcome, or deliverable'),
      notes: z.string().max(10000).optional().describe('Replace existing notes with new project description, objectives, or context (max 10,000 characters). Supports markdown formatting. This completely replaces existing notes'),
      prependNotes: z.string().optional().describe('Add text to the beginning of existing notes without replacing them. Useful for adding project updates or new objectives'),
      appendNotes: z.string().optional().describe('Add text to the end of existing notes without replacing them. Useful for adding progress updates or new requirements'),
      when: z.enum(['today', 'tomorrow', 'evening', 'anytime', 'someday'])
        .or(z.string().regex(/^\d{4}-\d{2}-\d{2}$/))
        .optional()
        .describe('Reschedule 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'),
      deadline: z.string()
        .regex(/^\d{4}-\d{2}-\d{2}$/)
        .optional()
        .describe('Update the project deadline in ISO date format (YYYY-MM-DD). Creates or updates deadline tracking and reminders in Things.app'),
      tags: z.array(z.string().min(1))
        .max(20)
        .optional()
        .describe('Replace all current tags with this new set of tag names (max 20 tags). This completely replaces existing tags for the project'),
      addTags: z.array(z.string().min(1))
        .max(20)
        .optional()
        .describe('Add these tag names to existing tags without removing current ones (max 20 total tags). Preserves existing project tags'),
      areaId: z.string()
        .optional()
        .describe('Move the project to a different area of responsibility by specifying the area ID'),
      areaName: z.string()
        .optional()
        .describe('Move the project to a different area of responsibility by specifying the area name (e.g., "Work", "Personal", "Health", "Finance")'),
      completed: z.boolean()
        .optional()
        .describe('Mark the project as completed (true) or reopen it (false). Completed projects are moved to the Logbook along with all their to-dos'),
      canceled: z.boolean()
        .optional()
        .describe('Mark the project as canceled (true) or restore it (false). Canceled projects are moved to the Trash along with all their to-dos'),
      creationDate: z.string()
        .regex(/^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}/)
        .optional()
        .describe('Override the creation date with a specific ISO8601 datetime (YYYY-MM-DDTHH:MM:SS). Useful for data migration or historical project tracking'),
      completionDate: z.string()
        .regex(/^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}/)
        .optional()
        .describe('Set a specific completion date using ISO8601 datetime (YYYY-MM-DDTHH:MM:SS). Only used when marking the project as completed')
    });
  • The registration function that registers the 'update_project' tool on the MCP server using server.tool(), providing name, description, input schema, and handler.
    export function registerUpdateProjectTool(server: McpServer): void {
      server.tool(
        'update_project',
        'Update an existing project in Things.app. Modify title, notes, scheduling, tags, area assignment, and completion status.',
        updateProjectSchema.shape,
        async (params) => {
          try {
            logger.info('Updating project', { id: params.id });
            
            const authToken = requireAuthToken();
            
            // Check if we're doing a completion/cancellation operation (use JSON)
            if (params.completed !== undefined || params.canceled !== undefined) {
              const attributes: Record<string, any> = {};
              
              if (params.completed !== undefined) {
                attributes.completed = params.completed;
                if (params.completionDate) {
                  attributes['completion-date'] = params.completionDate;
                }
              }
              
              if (params.canceled !== undefined) {
                attributes.canceled = params.canceled;
              }
              
              const operation: JsonOperation = {
                type: 'project',
                operation: 'update',
                id: params.id,
                attributes
              };
              
              await executeJsonOperation(operation, authToken);
            } else {
              // Use URL scheme for other updates
              const urlParams: Record<string, any> = {
                id: params.id,
                'auth-token': authToken
              };
    
              // Map schema parameters to Things URL scheme parameters
              if (params.title) urlParams.title = params.title;
              if (params.notes) urlParams.notes = params.notes;
              if (params.prependNotes) urlParams['prepend-notes'] = params.prependNotes;
              if (params.appendNotes) urlParams['append-notes'] = params.appendNotes;
              if (params.when) urlParams.when = params.when;
              if (params.deadline) urlParams.deadline = params.deadline;
              if (params.tags) urlParams.tags = params.tags.join(',');
              if (params.addTags) urlParams['add-tags'] = params.addTags.join(',');
              if (params.areaId) urlParams['area-id'] = params.areaId;
              if (params.areaName) urlParams.area = params.areaName;
              if (params.creationDate) urlParams['creation-date'] = params.creationDate;
              
              const url = buildThingsUrl('update-project', urlParams);
              logger.debug('Generated URL', { url: url.replace(authToken, '***') });
              
              await openThingsUrl(url);
            }
            
            return {
              content: [{
                type: "text",
                text: `Successfully updated project: ${params.id}`
              }]
            };
          } catch (error) {
            logger.error('Failed to update project', { error: error instanceof Error ? error.message : error });
            throw error;
          }
        }
      );
    }
  • src/index.ts:24-24 (registration)
    Top-level call to register the update_project tool during server initialization.
    registerUpdateProjectTool(server);
  • TypeScript interface defining parameters for project updates, used in URL building or related utilities.
    export interface UpdateProjectParams {
      id: string;
      'auth-token': string;
      title?: string;
      notes?: string;
      when?: WhenValue;
      deadline?: string;
      tags?: string;
      area?: string;
      completed?: boolean;
      canceled?: boolean;
      'prepend-notes'?: string;
      'append-notes'?: string;
      'add-tags'?: string;
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Update' implies a mutation operation, the description fails to mention critical behavioral aspects such as required permissions, whether changes are reversible, error handling, or what happens to unspecified fields. For a complex mutation tool with 15 parameters, this leaves significant gaps in understanding how the tool behaves.

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 a single, efficient sentence that front-loads the core purpose and enumerates the key modifiable fields. Every word serves a purpose with zero waste, making it easy to parse quickly.

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 complex mutation tool with 15 parameters, no annotations, and no output schema, the description is inadequate. It doesn't address behavioral aspects like side effects, error conditions, or response format. While the schema covers parameter details well, the description fails to provide the broader context needed for safe and effective tool invocation.

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?

The schema description coverage is 100%, meaning all parameters are well-documented in the input schema itself. The description adds minimal value beyond what's already in the schema by listing the general categories of fields that can be modified. It doesn't provide additional semantic context or usage examples that aren't already covered by the detailed parameter descriptions.

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?

The description clearly states the verb ('Update') and resource ('an existing project in Things.app'), and lists the specific fields that can be modified (title, notes, scheduling, tags, area assignment, and completion status). However, it doesn't explicitly differentiate this tool from sibling tools like 'update_todo' or 'add_project' beyond the resource name, which prevents a perfect score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'add_project' or 'update_todo', nor does it mention any prerequisites or constraints. It simply states what the tool does without contextual usage information.

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