Skip to main content
Glama
makeplane

Plane MCP Server

Official
by makeplane

create_issue

Generate and submit new issues within the Plane MCP Server. Provide a project UUID and relevant issue details, including name and HTML description, to create and track tasks or problems efficiently.

Instructions

Create an issue. This requests project_id as uuid parameter. If you have a readable identifier for project, you can use the get_projects tool to get the project_id from it

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issue_dataYes
project_idYesThe uuid identifier of the project to create the issue for

Implementation Reference

  • Registers the 'create_issue' MCP tool with input schema (project_id and partial IssueSchema requiring name and description_html) and handler that POSTs to Plane API.
    server.tool(
      "create_issue",
      "Create an issue. This requests project_id as uuid parameter. If you have a readable identifier for project, you can use the get_projects tool to get the project_id from it",
      {
        project_id: z.string().describe("The uuid identifier of the project to create the issue for"),
        issue_data: IssueSchema.partial().required({
          name: true,
          description_html: true,
        }),
      },
      async ({ project_id, issue_data }) => {
        const response = await makePlaneRequest(
          "POST",
          `workspaces/${process.env.PLANE_WORKSPACE_SLUG}/projects/${project_id}/issues/`,
          issue_data
        );
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(response, null, 2),
            },
          ],
        };
      }
    );
  • Handler function executes the tool by sending a POST request to the Plane issues endpoint with the provided project_id and issue_data, returning the response as text content.
      async ({ project_id, issue_data }) => {
        const response = await makePlaneRequest(
          "POST",
          `workspaces/${process.env.PLANE_WORKSPACE_SLUG}/projects/${project_id}/issues/`,
          issue_data
        );
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(response, null, 2),
            },
          ],
        };
      }
    );
  • Zod schema definition for Issue type (imported as IssueSchema), used for validating issue_data input in create_issue tool.
    export const Issue = z.object({
      archived_at: z.string().date().optional(),
      assignees: z.array(z.string().uuid()).optional(),
      completed_at: z.string().datetime({ offset: true }).optional(),
      created_at: z.string().datetime({ offset: true }).readonly(),
      created_by: z.string().uuid().optional(),
      deleted_at: z.string().datetime({ offset: true }).optional(),
      description_binary: z.string().readonly(),
      description_html: z.string().optional(),
      estimate_point: z.string().uuid().optional(),
      external_id: z.string().max(255).optional(),
      external_source: z.string().max(255).optional(),
      id: z.string().uuid().readonly(),
      is_draft: z.boolean().optional(),
      labels: z.array(z.string().uuid()).optional(),
      name: z.string().max(255),
      parent: z.string().uuid().optional(),
      point: z.number().int().gte(0).lte(12).optional(),
      priority: z.any().optional(),
      project: z.string().uuid().readonly(),
      sequence_id: z.number().int().gte(-2147483648).lte(2147483647).optional(),
      sort_order: z.number().optional(),
      start_date: z.string().date().optional(),
      state: z.string().uuid().optional(),
      target_date: z.string().date().optional(),
      type: z.string().uuid().optional(),
      type_id: z.string().uuid().optional(),
      updated_at: z.string().datetime({ offset: true }).readonly(),
      updated_by: z.string().uuid().readonly(),
      workspace: z.string().uuid().readonly(),
    });
    export type Issue = z.infer<typeof Issue>;
  • Higher-level registration calls registerIssueTools(server), which includes the create_issue tool.
    registerIssueTools(server);
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 a creation operation but doesn't mention permission requirements, whether this creates a draft vs. published issue, what happens on success/failure, or any rate limits. The description mentions the project_id parameter but doesn't explain the creation behavior beyond that.

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 appropriately brief (two sentences) and front-loaded with the core purpose. The second sentence provides useful guidance without unnecessary elaboration. However, it could be slightly more structured by separating parameter guidance from the main purpose.

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 creation tool with no annotations, no output schema, and complex nested parameters (26 properties in issue_data), the description is inadequate. It doesn't explain what constitutes a valid issue, what fields are required vs. optional beyond schema requirements, what the tool returns, or any behavioral aspects of the creation operation.

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 50% (only project_id has a description). The description adds that 'This requests project_id as uuid parameter' and provides guidance about using get_projects to obtain it. However, it doesn't explain the complex issue_data object with its 26 properties, leaving most parameters undocumented. The description adds some value but doesn't compensate for the low schema coverage.

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 'Create an issue' which is a clear verb+resource, but it doesn't specify what an 'issue' represents in this context or differentiate it from similar creation tools like 'create_project' or 'create_label'. The purpose is understandable but lacks specificity about the domain or 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 Guidelines4/5

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

The description provides explicit guidance on when to use this tool: 'If you have a readable identifier for project, you can use the get_projects tool to get the project_id from it'. This tells the agent about a prerequisite step and references a specific sibling tool (get_projects). However, it doesn't mention when NOT to use this tool or alternatives for similar operations.

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/makeplane/plane-mcp-server'

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