Skip to main content
Glama
jhirono

Microsoft Todo MCP Service

update-task-list

Modify the name of an existing Microsoft Todo task list container by providing its ID and new display name.

Instructions

Update the name of an existing task list (top-level container) in Microsoft Todo.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
listIdYesID of the task list to update
displayNameYesNew name for the task list

Implementation Reference

  • Complete implementation of the 'update-task-list' tool: registers the tool with MCP server, defines input schema (listId, displayName), and provides the handler function that authenticates via getAccessToken, makes a PATCH request to Microsoft Graph API endpoint /me/todo/lists/{listId} to update the displayName, and returns success/error messages.
    server.tool(
      "update-task-list",
      "Update the name of an existing task list (top-level container) in Microsoft Todo.",
      {
        listId: z.string().describe("ID of the task list to update"),
        displayName: z.string().describe("New name for the task list")
      },
      async ({ listId, displayName }) => {
        try {
          const token = await getAccessToken();
          if (!token) {
            return {
              content: [
                {
                  type: "text",
                  text: "Failed to authenticate with Microsoft API",
                },
              ],
            };
          }
    
          // Prepare the request body
          const requestBody = {
            displayName
          };
    
          // Make the API request to update the task list
          const response = await makeGraphRequest<TaskList>(
            `${MS_GRAPH_BASE}/me/todo/lists/${listId}`,
            token,
            "PATCH",
            requestBody
          );
          
          if (!response) {
            return {
              content: [
                {
                  type: "text",
                  text: `Failed to update task list with ID: ${listId}`,
                },
              ],
            };
          }
    
          return {
            content: [
              {
                type: "text",
                text: `Task list updated successfully!\nNew name: ${response.displayName}`,
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error updating task list: ${error}`,
              },
            ],
          };
        }
      }
    );
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is an update operation (implying mutation) but doesn't describe permissions needed, whether changes are reversible, rate limits, error responses, or what happens on success. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 purpose and includes necessary context ('Microsoft Todo', 'top-level container'). Every element earns its place without redundancy.

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 insufficient. It doesn't explain what the tool returns, error conditions, or behavioral implications. While the schema covers parameters well, the overall context for using this update operation remains incomplete 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 description coverage is 100%, so the schema already fully documents both parameters (listId and displayName). The description adds no additional parameter semantics beyond what's in the schema - it doesn't explain format requirements, constraints, or examples. Baseline 3 is appropriate when the schema does all the parameter documentation work.

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 ('Update'), the resource ('name of an existing task list'), and the platform context ('Microsoft Todo'). It specifies this is for 'top-level container' task lists, which helps distinguish it from other list-like resources. However, it doesn't explicitly differentiate from sibling 'update-task' or 'update-checklist-item' tools beyond the resource type.

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-checklist-item'. It doesn't mention prerequisites (e.g., needing an existing list ID), error conditions, or when not to use it. The only contextual clue is 'existing task list', implying the list must already exist.

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