Skip to main content
Glama
jhirono

Microsoft Todo MCP Service

update-checklist-item

Modify checklist item details in Microsoft Todo by updating text content or marking completion status to track subtask progress.

Instructions

Update an existing checklist item (subtask). Allows changing the text content or completion status of the subtask.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
listIdYesID of the task list
taskIdYesID of the task
checklistItemIdYesID of the checklist item to update
displayNameNoNew text content of the checklist item
isCheckedNoWhether the item is checked off

Implementation Reference

  • Full implementation of the 'update-checklist-item' MCP tool handler. Registers the tool with server.tool(), defines input schema using Zod for parameters (listId, taskId, checklistItemId, optional displayName and isChecked), and implements the async handler that authenticates, prepares PATCH body, calls makeGraphRequest to Microsoft Graph API endpoint /me/todo/lists/{listId}/tasks/{taskId}/checklistItems/{checklistItemId}, and returns success/error messages.
    server.tool(
      "update-checklist-item",
      "Update an existing checklist item (subtask). Allows changing the text content or completion status of the subtask.",
      {
        listId: z.string().describe("ID of the task list"),
        taskId: z.string().describe("ID of the task"),
        checklistItemId: z.string().describe("ID of the checklist item to update"),
        displayName: z.string().optional().describe("New text content of the checklist item"),
        isChecked: z.boolean().optional().describe("Whether the item is checked off")
      },
      async ({ listId, taskId, checklistItemId, displayName, isChecked }) => {
        try {
          const token = await getAccessToken();
          if (!token) {
            return {
              content: [
                {
                  type: "text",
                  text: "Failed to authenticate with Microsoft API",
                },
              ],
            };
          }
    
          // Prepare the update body, including only the fields that are provided
          const requestBody: any = {};
          
          if (displayName !== undefined) {
            requestBody.displayName = displayName;
          }
          
          if (isChecked !== undefined) {
            requestBody.isChecked = isChecked;
          }
          
          // Make sure we have at least one property to update
          if (Object.keys(requestBody).length === 0) {
            return {
              content: [
                {
                  type: "text",
                  text: "No properties provided for update. Please specify either displayName or isChecked.",
                },
              ],
            };
          }
    
          // Make the API request to update the checklist item
          const response = await makeGraphRequest<ChecklistItem>(
            `${MS_GRAPH_BASE}/me/todo/lists/${listId}/tasks/${taskId}/checklistItems/${checklistItemId}`,
            token,
            "PATCH",
            requestBody
          );
          
          if (!response) {
            return {
              content: [
                {
                  type: "text",
                  text: `Failed to update checklist item with ID: ${checklistItemId}`,
                },
              ],
            };
          }
    
          const statusText = response.isChecked ? "Checked" : "Not checked";
          
          return {
            content: [
              {
                type: "text",
                text: `Checklist item updated successfully!\nContent: ${response.displayName}\nStatus: ${statusText}`,
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error updating checklist item: ${error}`,
              },
            ],
          };
        }
      }
    );
  • Zod schema definition for the input parameters of the update-checklist-item tool.
    {
      listId: z.string().describe("ID of the task list"),
      taskId: z.string().describe("ID of the task"),
      checklistItemId: z.string().describe("ID of the checklist item to update"),
      displayName: z.string().optional().describe("New text content of the checklist item"),
      isChecked: z.boolean().optional().describe("Whether the item is checked off")
    },
  • Registration of the 'update-checklist-item' tool using server.tool().
    server.tool(
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. It states this is an update operation, implying mutation, but doesn't cover permissions needed, whether changes are reversible, error handling, or response format. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 purpose and key capabilities without waste. Every word contributes to understanding the tool's function, making it appropriately sized and well-structured.

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?

Given this is a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits (e.g., permissions, side effects), response format, and usage context relative to siblings. While the schema covers parameters well, the overall context for safe and effective use is insufficient.

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 the schema already documents all 5 parameters thoroughly. The description adds minimal value by mentioning 'text content' (mapping to displayName) and 'completion status' (mapping to isChecked), but doesn't provide additional syntax or context beyond what the schema offers. Baseline 3 is appropriate when 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 verb ('update') and resource ('existing checklist item/subtask'), specifying what can be changed ('text content or completion status'). It distinguishes from siblings like create-checklist-item or delete-checklist-item by focusing on modification rather than creation or removal, though it doesn't explicitly contrast with update-task or update-task-list.

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 update-task or update-task-list, nor does it mention prerequisites or exclusions. It implies usage for modifying subtasks but lacks context about sibling relationships or specific scenarios.

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/jhirono/todoMCP'

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