Skip to main content
Glama

updateTask

Modify task details in Godspeed MCP server, including labels, due dates, status, notes, and metadata, using the task ID for precise updates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
add_label_idsNo
add_label_namesNo
due_atNo
duration_minutesNo
idYes
is_clearedNo
is_completeNo
metadataNo
notesNo
remove_label_idsNo
remove_label_namesNo
snoozed_untilNo
starts_atNo
timeless_due_atNo
timeless_snoozed_untilNo
timeless_starts_atNo
titleNo

Implementation Reference

  • MCP tool handler function for 'updateTask' that delegates to GodspeedAPI.updateTask, formats the result as JSON text content, and handles errors.
    async (params) => {
        try {
            const result = await godspeedApi.updateTask(params);
            return {
                content: [{ type: "text", text: JSON.stringify(result, null, 2) }]
            };
        } catch (error) {
            return {
                content: [{ type: "text", text: `Error: ${error instanceof Error ? error.message : String(error)}` }]
            };
        }
    }
  • Zod input schema for the 'updateTask' MCP tool parameters.
        id: z.string(),
        title: z.string().optional(),
        notes: z.string().optional(),
        due_at: z.date().optional(),
        timeless_due_at: z.string().optional(),
        snoozed_until: z.date().optional(),
        timeless_snoozed_until: z.string().optional(),
        starts_at: z.date().optional(),
        timeless_starts_at: z.string().optional(),
        duration_minutes: z.number().int().nonnegative().optional(),
        is_complete: z.boolean().optional(),
        is_cleared: z.boolean().optional(),
        add_label_names: z.array(z.string()).optional(),
        add_label_ids: z.array(z.string()).optional(),
        remove_label_names: z.array(z.string()).optional(),
        remove_label_ids: z.array(z.string()).optional(),
        metadata: z.record(z.any()).optional()
    },
  • src/index.ts:117-150 (registration)
    Registration of the 'updateTask' tool using McpServer.tool, including schema and handler.
    server.tool(
        "updateTask",
        {
            id: z.string(),
            title: z.string().optional(),
            notes: z.string().optional(),
            due_at: z.date().optional(),
            timeless_due_at: z.string().optional(),
            snoozed_until: z.date().optional(),
            timeless_snoozed_until: z.string().optional(),
            starts_at: z.date().optional(),
            timeless_starts_at: z.string().optional(),
            duration_minutes: z.number().int().nonnegative().optional(),
            is_complete: z.boolean().optional(),
            is_cleared: z.boolean().optional(),
            add_label_names: z.array(z.string()).optional(),
            add_label_ids: z.array(z.string()).optional(),
            remove_label_names: z.array(z.string()).optional(),
            remove_label_ids: z.array(z.string()).optional(),
            metadata: z.record(z.any()).optional()
        },
        async (params) => {
            try {
                const result = await godspeedApi.updateTask(params);
                return {
                    content: [{ type: "text", text: JSON.stringify(result, null, 2) }]
                };
            } catch (error) {
                return {
                    content: [{ type: "text", text: `Error: ${error instanceof Error ? error.message : String(error)}` }]
                };
            }
        }
    );
  • Core helper function in GodspeedAPI class that validates parameters and performs the PATCH request to update a task via the Godspeed API.
    async updateTask(params: UpdateTaskParams): Promise<ApiResponse<Task>> {
        try {
            const headers = this.getAuthHeaders();
    
            // Validate required parameters
            if (!params.id) {
                throw new Error('Task ID is required');
            }
    
            // Validate conflicting date parameters
            if (params.due_at && params.timeless_due_at) {
                throw new Error('Cannot specify both due_at and timeless_due_at');
            }
    
            if (params.snoozed_until && params.timeless_snoozed_until) {
                throw new Error('Cannot specify both snoozed_until and timeless_snoozed_until');
            }
    
            if (params.starts_at && params.timeless_starts_at) {
                throw new Error('Cannot specify both starts_at and timeless_starts_at');
            }
    
            // Validate timeless date formats if provided
            if (params.timeless_due_at && !/^\d{4}-\d{2}-\d{2}$/.test(params.timeless_due_at)) {
                throw new Error('timeless_due_at must be formatted as YYYY-MM-DD');
            }
    
            if (params.timeless_snoozed_until && !/^\d{4}-\d{2}-\d{2}$/.test(params.timeless_snoozed_until)) {
                throw new Error('timeless_snoozed_until must be formatted as YYYY-MM-DD');
            }
    
            if (params.timeless_starts_at && !/^\d{4}-\d{2}-\d{2}$/.test(params.timeless_starts_at)) {
                throw new Error('timeless_starts_at must be formatted as YYYY-MM-DD');
            }
    
            // Validate duration_minutes if provided
            if (params.duration_minutes !== undefined && (!Number.isInteger(params.duration_minutes) || params.duration_minutes < 0)) {
                throw new Error('duration_minutes must be a positive integer');
            }
    
            const { id, ...updateData } = params;
    
            const response = await fetch(`${API_BASE_URL}/tasks/${id}`, {
                method: 'PATCH',
                headers,
                body: JSON.stringify(updateData),
            });
    
            const data = await response.json();
    
            if (!response.ok) {
                throw new Error(data.error || 'Failed to update task');
            }
    
            return data;
        } catch (error) {
            throw new Error(`Update task error: ${error instanceof Error ? error.message : String(error)}`);
        }
    }
  • TypeScript type definition for UpdateTaskParams used in the GodspeedAPI.updateTask method.
    export interface UpdateTaskParams {
        id: string;
        title?: string;
        notes?: string;
        due_at?: Date;
        timeless_due_at?: string;
        snoozed_until?: Date;
        timeless_snoozed_until?: string;
        starts_at?: Date;
        timeless_starts_at?: string;
        duration_minutes?: number;
        is_complete?: boolean;
        is_cleared?: boolean;
        add_label_names?: string[];
        add_label_ids?: string[];
        remove_label_names?: string[];
        remove_label_ids?: string[];
        metadata?: Record<string, any>;
    }
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

Related 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/AliNagy/godspeed-mcp'

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