Skip to main content
Glama

list-issues

Retrieve and filter project issues from Plane.so by project ID, with options to sort by state, priority, assignee, and limit results.

Instructions

List issues from a project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesID of the project to get issues from
state_idNoFilter by state ID (optional)
priorityNoFilter by priority (optional)
assignee_idNoFilter by assignee ID (optional)
limitNoMaximum number of issues to return (default: 50)

Implementation Reference

  • The switch case handler for executing the 'list-issues' tool. It validates the project_id, builds a query string from optional filters (state_id, priority, assignee_id, limit), calls the Plane API endpoint /projects/{project_id}/issues/ with the query, and returns the JSON response.
    case "list-issues": {
      if (!args || typeof args.project_id !== "string") {
        throw new Error("Project ID is required");
      }
      const { project_id, ...queryParams } = args;
    
      // Build query string from other parameters
      const queryString = Object.entries(queryParams)
        .filter(([_, value]) => value !== undefined)
        .map(([key, value]) => `${key}=${encodeURIComponent(String(value))}`)
        .join("&");
    
      const endpoint = `/projects/${project_id}/issues/${
        queryString ? `?${queryString}` : ""
      }`;
      const issues = await callPlaneAPI(endpoint, "GET");
    
      return {
        content: [{ type: "text", text: JSON.stringify(issues, null, 2) }],
        isError: false,
      };
    }
  • The Tool object definition for 'list-issues', specifying name, description, and inputSchema with required project_id and optional filters for state, priority, assignee, and limit.
    const LIST_ISSUES_TOOL: Tool = {
      name: "list-issues",
      description: "List issues from a project",
      inputSchema: {
        type: "object",
        properties: {
          project_id: {
            type: "string",
            description: "ID of the project to get issues from",
          },
          state_id: {
            type: "string",
            description: "Filter by state ID (optional)",
          },
          priority: {
            type: "string",
            description: "Filter by priority (optional)",
            enum: ["urgent", "high", "medium", "low", "none"],
          },
          assignee_id: {
            type: "string",
            description: "Filter by assignee ID (optional)",
          },
          limit: {
            type: "number",
            description: "Maximum number of issues to return (default: 50)",
          },
        },
        required: ["project_id"],
      },
    };
  • src/index.ts:262-271 (registration)
    Registration of available tools in the ListToolsRequestSchema handler, including the LIST_ISSUES_TOOL in the tools array returned to clients.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        LIST_PROJECTS_TOOL,
        GET_PROJECT_TOOL,
        CREATE_ISSUE_TOOL,
        LIST_ISSUES_TOOL,
        GET_ISSUE_TOOL,
        UPDATE_ISSUE_TOOL,
      ],
    }));
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 'List issues' but doesn't disclose behavioral traits like pagination (implied by 'limit'), default sorting, rate limits, authentication needs, or error handling. This leaves significant gaps for an agent to understand how the tool behaves.

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

Conciseness5/5

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

The description is a single, efficient sentence with zero waste. It's front-loaded and appropriately sized for a basic listing tool, making it easy to parse quickly.

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 no annotations and no output schema, the description is incomplete. It doesn't explain return values (e.g., issue format), pagination behavior, or error cases. For a tool with 5 parameters and no structured behavioral hints, this leaves the agent under-informed about critical usage aspects.

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. The description adds no meaning beyond the schema, such as explaining how filters combine or the format of returned issues. Baseline 3 is appropriate since the schema does the heavy lifting.

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 'List issues from a project' clearly states the verb ('List') and resource ('issues'), but it's vague about scope (e.g., all issues vs. filtered) and doesn't distinguish from siblings like 'get-issue' (single issue) or 'list-projects' (different resource). It's functional but lacks specificity.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't mention using 'get-issue' for a single issue or 'list-projects' to find project IDs first. The description implies usage for listing issues but offers no context on 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

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

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