Skip to main content
Glama
jhirono

Microsoft Todo MCP Service

create-task-list

Create a new task list in Microsoft Todo to organize tasks into categories or projects. Specify a display name to categorize your tasks effectively.

Instructions

Create a new task list (top-level container) in Microsoft Todo to help organize your tasks into categories or projects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
displayNameYesName of the new task list

Implementation Reference

  • The handler function that implements the core logic of the 'create-task-list' tool. It retrieves an access token, makes a POST request to the Microsoft Graph API endpoint `/me/todo/lists` with the provided displayName, handles errors, and returns a formatted success message with the new list's details.
    async ({ 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 create the task list
        const response = await makeGraphRequest<TaskList>(
          `${MS_GRAPH_BASE}/me/todo/lists`,
          token,
          "POST",
          requestBody
        );
        
        if (!response) {
          return {
            content: [
              {
                type: "text",
                text: `Failed to create task list: ${displayName}`,
              },
            ],
          };
        }
    
        return {
          content: [
            {
              type: "text",
              text: `Task list created successfully!\nName: ${response.displayName}\nID: ${response.id}`,
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: `Error creating task list: ${error}`,
            },
          ],
        };
      }
    }
  • The input schema for the 'create-task-list' tool, using Zod to validate the required 'displayName' parameter as a string.
    {
      displayName: z.string().describe("Name of the new task list")
    },
  • The registration of the 'create-task-list' tool on the MCP server using server.tool(), specifying the tool name, description, input schema, and handler function.
    server.tool(
      "create-task-list",
      "Create a new task list (top-level container) in Microsoft Todo to help organize your tasks into categories or projects.",
      {
        displayName: z.string().describe("Name of the new task list")
      },
      async ({ 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 create the task list
          const response = await makeGraphRequest<TaskList>(
            `${MS_GRAPH_BASE}/me/todo/lists`,
            token,
            "POST",
            requestBody
          );
          
          if (!response) {
            return {
              content: [
                {
                  type: "text",
                  text: `Failed to create task list: ${displayName}`,
                },
              ],
            };
          }
    
          return {
            content: [
              {
                type: "text",
                text: `Task list created successfully!\nName: ${response.displayName}\nID: ${response.id}`,
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error creating task list: ${error}`,
              },
            ],
          };
        }
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states this creates a 'top-level container,' implying a write operation, but doesn't disclose behavioral traits like required permissions, whether it's idempotent, error conditions, or what happens on success/failure. For a mutation tool with zero annotation coverage, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core action ('Create a new task list') and purpose. It avoids redundancy, but could be slightly more structured by separating usage context. Every word earns its place, making it concise.

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 the tool is a mutation (create operation) with no annotations, no output schema, and 1 parameter, the description is incomplete. It doesn't cover behavioral aspects like permissions, side effects, or response format, which are critical for an AI agent to invoke it correctly. The purpose is clear, but operational details are lacking.

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%, with the parameter 'displayName' documented as 'Name of the new task list.' The description adds no additional parameter semantics beyond this, such as format constraints or examples. With high schema coverage, the baseline is 3, 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 ('Create a new task list') and resource ('in Microsoft Todo'), with the purpose to 'organize your tasks into categories or projects.' It distinguishes from siblings like 'create-task' (individual tasks) and 'create-checklist-item' (items within lists), but doesn't explicitly contrast with 'get-task-lists' (read-only) or 'update-task-list' (modify existing).

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

Usage Guidelines3/5

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

The description implies usage for organizing tasks into categories/projects, suggesting when to use it. However, it lacks explicit guidance on when not to use it (e.g., vs. 'create-task' for standalone tasks) or alternatives like 'update-task-list' for modifying existing lists. The context is clear but not comprehensive.

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