Skip to main content
Glama
robertn702

Sunsama MCP Server

update-task-backlog

Move tasks to your backlog for later review and organization. This tool helps you defer tasks by transferring them from your active list to the backlog using the task ID.

Instructions

Move a task to the backlog

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitResponsePayloadNoWhether to limit the response payload size
taskIdYesThe ID of the task to move to backlog
timezoneNoTimezone string (e.g., 'America/New_York'). If not provided, uses user's default timezone

Implementation Reference

  • Main handler implementation for the 'update-task-backlog' tool. It moves a task to the backlog by calling `updateTaskSnoozeDate` with a null date.
    export const updateTaskBacklogTool = withTransportClient({
      name: "update-task-backlog",
      description: "Move a task to the backlog",
      parameters: updateTaskBacklogSchema,
      execute: async (
        { taskId, timezone, limitResponsePayload }: UpdateTaskBacklogInput,
        context: ToolContext,
      ) => {
        const options: { timezone?: string; limitResponsePayload?: boolean } = {};
        if (timezone) options.timezone = timezone;
        if (limitResponsePayload !== undefined) {
          options.limitResponsePayload = limitResponsePayload;
        }
    
        const result = await context.client.updateTaskSnoozeDate(
          taskId,
          null,
          options,
        );
    
        return formatJsonResponse({
          success: result.success,
          taskId,
          movedToBacklog: true,
          updatedFields: result.updatedFields,
        });
      },
    });
  • Zod schema defining the input parameters for the 'update-task-backlog' tool.
    // Update task backlog parameters
    export const updateTaskBacklogSchema = z.object({
      taskId: z.string().min(1, "Task ID is required").describe(
        "The ID of the task to move to backlog",
      ),
      timezone: z.string().optional().describe(
        "Timezone string (e.g., 'America/New_York'). If not provided, uses user's default timezone",
      ),
      limitResponsePayload: z.boolean().optional().describe(
        "Whether to limit the response payload size",
      ),
    });
  • The 'updateTaskBacklogTool' is registered in the taskTools array, which is re-exported from src/tools/index.ts into allTools.
    export const taskTools = [
      // Query tools
      getTasksBacklogTool,
      getTasksByDayTool,
      getArchivedTasksTool,
      getTaskByIdTool,
    
      // Lifecycle tools
      createTaskTool,
      deleteTaskTool,
    
      // Update tools
      updateTaskCompleteTool,
      updateTaskSnoozeDateTool,
      updateTaskBacklogTool,
      updateTaskPlannedTimeTool,
      updateTaskNotesTool,
      updateTaskDueDateTool,
      updateTaskTextTool,
      updateTaskStreamTool,
    ];
  • src/tools/index.ts:5-9 (registration)
    Top-level registration where taskTools (containing update-task-backlog) is spread into allTools.
    export const allTools = [
      ...userTools,
      ...taskTools,
      ...streamTools,
    ];
  • Imports helper functions like withTransportClient used to wrap the execute handler.
    import {
      formatJsonResponse,
      formatPaginatedTsvResponse,
      formatTsvResponse,
      withTransportClient,
      type ToolContext,
    } from "./shared.js";
Behavior2/5

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

With no annotations, the description carries full burden but only states the action without behavioral details. It doesn't disclose permissions needed, whether the move is reversible, side effects (e.g., clears due dates), or error conditions (e.g., invalid taskId). This is inadequate for a mutation tool.

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 with zero wasted words. It's front-loaded with the core action, making it easy to scan and understand 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 mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits, usage context, and what to expect upon success or failure. Given the complexity of task state changes, more guidance is needed.

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 description coverage is 100%, so parameters are fully documented in the schema. The description adds no additional meaning beyond implying 'taskId' is required, which is already clear from the schema. Baseline 3 is appropriate as the schema does the heavy lifting.

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 action ('Move') and target resource ('a task to the backlog'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'update-task-stream' or 'update-task-due-date', which also modify task states but to different destinations.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't mention prerequisites (e.g., task must not already be in backlog), exclusions (e.g., archived tasks), or related tools like 'get-tasks-backlog' for viewing backlogged tasks.

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/robertn702/mcp-sunsama'

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