Skip to main content
Glama
makeplane

Plane MCP Server

Official
by makeplane

update_issue

Modify issue details in Plane MCP Server by providing project_id, issue_id, and updated issue_data, including attributes like assignees, labels, and target dates.

Instructions

Update an issue. This requests project_id and issue_id as uuid parameters. If you have a readable identifier, you can use the get_issue_using_readable_identifier tool to get the issue_id and project_id

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issue_dataYesThe fields to update on the issue
issue_idYesThe uuid identifier of the issue to update
project_idYesThe uuid identifier of the project containing the issue

Implementation Reference

  • The async handler function that executes the tool by sending a PATCH request to update the issue via the Plane API.
    async ({ project_id, issue_id, issue_data }) => {
      const response = await makePlaneRequest(
        "PATCH",
        `workspaces/${process.env.PLANE_WORKSPACE_SLUG}/projects/${project_id}/issues/${issue_id}/`,
        issue_data
      );
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response, null, 2),
          },
        ],
      };
    }
  • Input schema/validation for the update_issue tool parameters.
    {
      project_id: z.string().describe("The uuid identifier of the project containing the issue"),
      issue_id: z.string().describe("The uuid identifier of the issue to update"),
      issue_data: IssueSchema.partial().describe("The fields to update on the issue"),
    },
  • Registration of the 'update_issue' tool using McpServer.tool() method inside registerIssueTools function.
    server.tool(
      "update_issue",
      "Update an issue. This requests project_id and issue_id as uuid parameters. If you have a readable identifier, you can use the get_issue_using_readable_identifier tool to get the issue_id and project_id",
      {
        project_id: z.string().describe("The uuid identifier of the project containing the issue"),
        issue_id: z.string().describe("The uuid identifier of the issue to update"),
        issue_data: IssueSchema.partial().describe("The fields to update on the issue"),
      },
      async ({ project_id, issue_id, issue_data }) => {
        const response = await makePlaneRequest(
          "PATCH",
          `workspaces/${process.env.PLANE_WORKSPACE_SLUG}/projects/${project_id}/issues/${issue_id}/`,
          issue_data
        );
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(response, null, 2),
            },
          ],
        };
      }
    );
  • Zod schema for Issue object, referenced as IssueSchema and used in partial form for update_issue input.
    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>;
  • High-level registration call to registerIssueTools(server), which includes the update_issue tool.
    registerIssueTools(server);
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states this is an update operation but provides no behavioral context about permissions needed, whether changes are reversible, rate limits, or what happens to unspecified fields. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 efficiently structured in two sentences. The first sentence states the purpose, and the second provides important usage guidance about parameter preparation. There's no wasted text, though it could be slightly more comprehensive without sacrificing 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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns, what permissions are required, or the behavioral implications of updating various fields. The 100% schema coverage helps with parameters, but overall context for safe and effective use is 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?

Schema description coverage is 100%, so the schema already documents all three parameters thoroughly. The description adds minimal value beyond the schema: it mentions that project_id and issue_id are UUID parameters and suggests an alternative tool for readable identifiers. This doesn't provide additional semantic context about the issue_data parameter or update behavior, so baseline 3 is appropriate.

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 ('an issue'), making the purpose immediately understandable. It distinguishes from sibling tools like 'create_issue' by focusing on modification rather than creation. However, it doesn't specify what fields can be updated or the scope of changes, which prevents a perfect score.

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 versus an alternative: it mentions that if you have a readable identifier instead of UUIDs, you should use 'get_issue_using_readable_identifier' first. This is helpful context for parameter preparation. However, it doesn't mention when NOT to use this tool (e.g., vs. delete_issue) or other alternatives among siblings.

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