Skip to main content
Glama
ParasSolanki

Jira MCP Server

by ParasSolanki

list_projects

Retrieve and filter Jira projects to manage workflows, track progress, and organize tasks with customizable parameters for results and details.

Instructions

List projects from Jira

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxResultsNoThe maximum number of results to return, (max: 100)
queryNoA query string used to filter the returned projects. The query string cannot be used with the startAt and maxResults parameters.
expandNoUse this parameter to include additional information in the response. This parameter accepts a comma-separated list. Expand options include: `description`, `lead`, `issueTypes`, `url`, `projectKeys`, `permissions`, `insight`. Comma separated list of options.

Implementation Reference

  • The main handler function for the 'list_projects' tool. It constructs a Jira API URL for listing projects, adds optional query parameters (maxResults, query, expand), fetches the data using $jiraJson, and returns the result wrapped in ok/err.
    export async function listProjects(input: ListProjectsInput) {
      const url = new URL(`/rest/api/2/project`, env.JIRA_BASE_URL);
    
      if (input.maxResults)
        url.searchParams.set("maxResults", input.maxResults.toString());
    
      if (input.query) url.searchParams.set("query", input.query);
    
      if (input.expand) url.searchParams.set("expand", input.expand);
    
      const json = await $jiraJson(url.toString());
    
      if (json.isErr()) return err(json.error);
    
      return ok(json.value);
    }
  • Zod schema defining the input parameters for the list_projects tool: optional maxResults (number), query (string), and expand (string).
    export const listProjectsInputSchema = z.object({
      maxResults: z
        .number()
        .optional()
        .describe("The maximum number of results to return, (max: 100)"),
      query: z
        .string()
        .optional()
        .describe(
          "A query string used to filter the returned projects. The query string cannot be used with the startAt and maxResults parameters.",
        ),
      expand: z
        .string()
        .optional()
        .describe(
          "Use this parameter to include additional information in the response. This parameter accepts a comma-separated list. Expand options include: `description`, `lead`, `issueTypes`, `url`, `projectKeys`, `permissions`, `insight`. Comma separated list of options.",
        ),
    });
  • Tool registration object defining the name, description, and input schema for the 'list_projects' tool.
    export const LIST_PROJECTS_TOOL: Tool = {
      name: "list_projects",
      description: "List projects from Jira",
      inputSchema: zodToJsonSchema(listProjectsInputSchema) as Tool["inputSchema"],
    };
  • src/app.ts:39-48 (registration)
    Central registration of all tools in the MCP server, including LIST_PROJECTS_TOOL, provided via listTools endpoint.
    export const tools = [
      // list
      LIST_PROJECTS_TOOL,
      LIST_BOARDS_TOOL,
      LIST_SPRINTS_FROM_BOARD_TOOL,
      LIST_ISSUES_FROM_SPRINT_TOOL,
    
      // create
      CREATE_ISSUE_TOOL,
    ] satisfies Tool[];
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 of behavioral disclosure. It states 'List projects from Jira', implying a read-only operation, but does not cover important aspects like pagination behavior, rate limits, authentication needs, or what the response includes (e.g., project details). This is a significant gap for a tool with no annotation coverage.

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 extremely concise with a single sentence, 'List projects from Jira', which is front-loaded and wastes no words. It efficiently conveys the core purpose without unnecessary elaboration, earning a high score for brevity and clarity.

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 (3 parameters, no annotations, no output schema), the description is incomplete. It does not explain return values, error handling, or behavioral traits like pagination. While the schema covers parameters well, the lack of output information and behavioral context leaves gaps for effective agent 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?

The input schema has 100% description coverage, with clear documentation for all three parameters (maxResults, query, expand). The description adds no additional meaning beyond the schema, such as examples or usage tips. According to the rules, with high schema coverage (>80%), the baseline score is 3, as 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 projects from Jira' clearly states the verb ('List') and resource ('projects from Jira'), making the purpose understandable. However, it lacks specificity about scope (e.g., all projects vs. filtered) and does not differentiate from sibling tools like 'list_boards' or 'list_issues_from_sprint', which list different Jira resources.

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 does not mention sibling tools like 'list_boards' for boards or 'list_issues_from_sprint' for issues, nor does it specify prerequisites or contexts for usage, leaving the agent without clear direction.

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/ParasSolanki/jira-mcp-server'

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