Skip to main content
Glama
makeplane

Plane MCP Server

Official
by makeplane

get_issue_using_readable_identifier

Retrieve specific project issues by providing a project identifier (e.g., FIRST) and issue identifier (e.g., 123) using the Plane MCP Server.

Instructions

Get all issues for a specific project. When issue identifier is provided something like FIRST-123, ABC-123, etc. For FIRST-123, project_identifier is FIRST and issue_identifier is 123

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issue_identifierYesThe identifier of the issue to get
project_identifierYesThe readable identifier of the project to get issues for

Implementation Reference

  • The core handler logic that takes project_identifier and issue_identifier, constructs the readable issue path, fetches the issue using makePlaneRequest, and returns it as JSON text content.
    async ({ project_identifier, issue_identifier }) => {
      const issue = await makePlaneRequest(
        "GET",
        `workspaces/${process.env.PLANE_WORKSPACE_SLUG}/issues/${project_identifier}-${issue_identifier}/`
      );
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(issue, null, 2),
          },
        ],
      };
    }
  • Zod input schema validating project_identifier and issue_identifier parameters.
    {
      project_identifier: z.string().describe("The readable identifier of the project (e.g., 'FIRST' for FIRST-123)"),
      issue_identifier: z.string().describe("The issue number (e.g., '123' for FIRST-123)"),
    },
  • Direct registration of the tool via McpServer.tool() call within registerIssueTools function.
    server.tool(
      "get_issue_using_readable_identifier",
      "Get a specific issue using its readable identifier. When issue identifier is provided something like FIRST-123, ABC-123, etc. For FIRST-123, project_identifier is FIRST and issue_identifier is 123",
      {
        project_identifier: z.string().describe("The readable identifier of the project (e.g., 'FIRST' for FIRST-123)"),
        issue_identifier: z.string().describe("The issue number (e.g., '123' for FIRST-123)"),
      },
      async ({ project_identifier, issue_identifier }) => {
        const issue = await makePlaneRequest(
          "GET",
          `workspaces/${process.env.PLANE_WORKSPACE_SLUG}/issues/${project_identifier}-${issue_identifier}/`
        );
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(issue, null, 2),
            },
          ],
        };
      }
    );
  • Helper utility function used by the tool handler to perform authenticated HTTP requests to the Plane API.
    export async function makePlaneRequest<T>(method: string, path: string, body: any = null): Promise<T> {
      const hostUrl = process.env.PLANE_API_HOST_URL || "https://api.plane.so/";
      const host = hostUrl.endsWith("/") ? hostUrl : `${hostUrl}/`;
      const url = `${host}api/v1/${path}`;
      const headers: Record<string, string> = {
        "X-API-Key": process.env.PLANE_API_KEY || "",
      };
    
      // Only add Content-Type for non-GET requests
      if (method.toUpperCase() !== "GET") {
        headers["Content-Type"] = "application/json";
      }
    
      try {
        const config: AxiosRequestConfig = {
          url,
          method,
          headers,
        };
    
        // Only include body for non-GET requests
        if (method.toUpperCase() !== "GET" && body !== null) {
          config.data = body;
        }
    
        const response = await axios(config);
        return response.data;
      } catch (error) {
        if (axios.isAxiosError(error)) {
          throw new Error(`Request failed: ${error.message}`);
        }
        throw error;
      }
    }
  • Top-level registration call to registerIssueTools(server), which includes the get_issue_using_readable_identifier tool, invoked from the main registerTools function.
    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 the full burden. It describes the tool as a 'Get' operation, implying read-only behavior, but doesn't disclose other traits like error handling, rate limits, authentication needs, or what happens if identifiers are invalid. The example clarifies identifier parsing but lacks broader behavioral context.

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 sized with two sentences: one stating the purpose and another explaining identifier parsing. It's front-loaded with the core function, and the second sentence adds necessary clarification without redundancy, making it efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (2 required parameters, no output schema, no annotations), the description is somewhat complete but has gaps. It covers the purpose and parameter mapping but lacks usage guidelines, behavioral details, and output information, leaving the agent with incomplete context for effective use.

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 both parameters. The description adds value by explaining how identifiers like 'FIRST-123' map to parameters (project_identifier as 'FIRST', issue_identifier as '123'), but this is a minor enhancement beyond the schema's basic descriptions.

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 tool's purpose: 'Get all issues for a specific project' with a specific verb ('Get') and resource ('issues'), and it distinguishes itself by focusing on readable identifiers. However, it doesn't explicitly differentiate from sibling tools like 'get_issue_comments' or 'get_issue_worklogs' beyond the identifier focus.

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 mentions the format of identifiers but doesn't explain when to choose this over other issue-related tools like 'get_issue_comments' or 'get_issue_worklogs', nor does it specify prerequisites or exclusions.

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