Skip to main content
Glama
gcorroto

Planka MCP Server

by gcorroto

mcp_kanban_list_manager

Manage kanban lists by performing actions like creating, updating, deleting, or retrieving lists and their details directly within Planka Kanban boards.

Instructions

Manage kanban lists with various operations

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesThe action to perform
boardIdNoThe ID of the board
idNoThe ID of the list
nameNoThe name of the list
positionNoThe position of the list

Implementation Reference

  • Main handler function that dispatches list management operations (get_all, create, get_one, update, delete) by calling helper functions from the lists module.
    async (args) => {
      let result;
    
      switch (args.action) {
        case "get_all":
          if (!args.boardId)
            throw new Error("boardId is required for get_all action");
          result = await lists.getLists(args.boardId);
          break;
    
        case "create":
          if (!args.boardId || !args.name || args.position === undefined)
            throw new Error(
              "boardId, name, and position are required for create action"
            );
          result = await lists.createList({
            boardId: args.boardId,
            name: args.name,
            position: args.position,
          });
          break;
    
        case "get_one":
          if (!args.id) throw new Error("id is required for get_one action");
          result = await lists.getList(args.id);
          break;
    
        case "update":
          if (!args.id || !args.name || args.position === undefined)
            throw new Error(
              "id, name, and position are required for update action"
            );
          const { id, ...updateOptions } = args;
          result = await lists.updateList(id, {
            name: args.name,
            position: args.position,
          });
          break;
    
        case "delete":
          if (!args.id) throw new Error("id is required for delete action");
          result = await lists.deleteList(args.id);
          break;
    
        default:
          throw new Error(`Unknown action: ${args.action}`);
      }
    
      return {
        content: [{ type: "text", text: JSON.stringify(result) }],
      };
    }
  • Zod input schema defining parameters for the tool actions: action enum, id, boardId, name, position.
    {
      action: z
        .enum(["get_all", "create", "update", "delete", "get_one"])
        .describe("The action to perform"),
      id: z.string().optional().describe("The ID of the list"),
      boardId: z.string().optional().describe("The ID of the board"),
      name: z.string().optional().describe("The name of the list"),
      position: z.number().optional().describe("The position of the list"),
    },
  • index.ts:164-228 (registration)
    Registration of the mcp_kanban_list_manager tool on the MCP server, providing description, input schema, and handler function.
    server.tool(
      "mcp_kanban_list_manager",
      "Manage kanban lists with various operations",
      {
        action: z
          .enum(["get_all", "create", "update", "delete", "get_one"])
          .describe("The action to perform"),
        id: z.string().optional().describe("The ID of the list"),
        boardId: z.string().optional().describe("The ID of the board"),
        name: z.string().optional().describe("The name of the list"),
        position: z.number().optional().describe("The position of the list"),
      },
      async (args) => {
        let result;
    
        switch (args.action) {
          case "get_all":
            if (!args.boardId)
              throw new Error("boardId is required for get_all action");
            result = await lists.getLists(args.boardId);
            break;
    
          case "create":
            if (!args.boardId || !args.name || args.position === undefined)
              throw new Error(
                "boardId, name, and position are required for create action"
              );
            result = await lists.createList({
              boardId: args.boardId,
              name: args.name,
              position: args.position,
            });
            break;
    
          case "get_one":
            if (!args.id) throw new Error("id is required for get_one action");
            result = await lists.getList(args.id);
            break;
    
          case "update":
            if (!args.id || !args.name || args.position === undefined)
              throw new Error(
                "id, name, and position are required for update action"
              );
            const { id, ...updateOptions } = args;
            result = await lists.updateList(id, {
              name: args.name,
              position: args.position,
            });
            break;
    
          case "delete":
            if (!args.id) throw new Error("id is required for delete action");
            result = await lists.deleteList(args.id);
            break;
    
          default:
            throw new Error(`Unknown action: ${args.action}`);
        }
    
        return {
          content: [{ type: "text", text: JSON.stringify(result) }],
        };
      }
    );
  • Helper function to retrieve all lists for a given board ID, used in 'get_all' action.
    export async function getLists(boardId: string) {
        try {
            // Get the board which includes lists in the response
            const response = await plankaRequest(`/api/boards/${boardId}`);
    
            // Check if the response has the expected structure
            if (
                response &&
                typeof response === "object" &&
                "included" in response &&
                response.included &&
                typeof response.included === "object" &&
                "lists" in (response.included as Record<string, unknown>)
            ) {
                // Get the lists from the included property
                const lists = (response.included as Record<string, unknown>).lists;
                if (Array.isArray(lists)) {
                    return lists;
                }
            }
    
            // If we can't find lists in the expected format, return an empty array
            return [];
        } catch (error) {
            // If all else fails, return an empty array
            return [];
        }
    }
  • Helper function to create a new list in a board, used in 'create' action.
    export async function createList(options: CreateListOptions) {
        try {
            const response = await plankaRequest(
                `/api/boards/${options.boardId}/lists`,
                {
                    method: "POST",
                    body: {
                        name: options.name,
                        position: options.position,
                    },
                },
            );
            const parsedResponse = ListResponseSchema.parse(response);
            return parsedResponse.item;
        } catch (error) {
            throw new Error(
                `Failed to create list: ${
                    error instanceof Error ? error.message : String(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. 'Manage' implies both read and write operations, but it doesn't disclose behavioral traits like authentication needs, rate limits, error handling, or what happens during deletions. The description is too generic to inform the agent about the tool's behavior beyond basic CRUD operations.

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 directly states the tool's purpose. It's appropriately sized and front-loaded, with no wasted words, though it could be more specific to improve clarity without losing conciseness.

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's complexity (5 parameters, no annotations, no output schema), the description is incomplete. It lacks details on behavioral traits, usage context, and output expectations, making it inadequate for an agent to fully understand how to invoke the tool correctly in various scenarios.

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 fully documents all 5 parameters, including the action enum and other fields. The description adds no additional meaning beyond the schema, as it doesn't explain parameter interactions or usage examples. Baseline 3 is appropriate since the schema handles parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool 'Manage kanban lists with various operations', which identifies the resource (kanban lists) and implies multiple operations. However, it's vague about what 'manage' entails and doesn't distinguish this from sibling tools like mcp_kanban_card_manager or mcp_kanban_task_manager, which also manage different kanban components.

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. It doesn't mention sibling tools or clarify the scope of 'kanban lists' compared to other kanban-related tools, leaving the agent to infer usage from the action parameter alone.

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/gcorroto/mcp-planka'

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