Skip to main content
Glama
KS-GEN-AI

Jira MCP Server

by KS-GEN-AI

list_projects

Retrieve all Jira projects to view available workspaces and their details for project management and tracking.

Instructions

List all the projects on Jira on the api /rest/api/3/project. Do not use markdown in your query.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
number_of_resultsNoNumber of results to return

Implementation Reference

  • The main handler function 'listProjects' that fetches the list of projects from Jira API /rest/api/3/project using axios, with optional maxResults parameter.
    async function listProjects(number_of_results: number): Promise<any> {
      try {
        const params = {
          maxResults: number_of_results, // Adjust as needed
        };
    
        const response = await axios.get(`${JIRA_URL}/rest/api/3/project`, {
          headers: getAuthHeaders().headers,
          params,
        });
    
        return response.data;
      } catch (error: any) {
        //return the error in a json
        return {
          error: error.response.data,
        };
      }
    }
  • The input schema definition for the 'list_projects' tool, including name, description, and inputSchema with number_of_results.
      name: 'list_projects',
      description:
        'List all the projects on Jira on the api /rest/api/3/project. Do not use markdown in your query.',
      inputSchema: {
        type: 'object',
        properties: {
          number_of_results: {
            type: 'integer',
            description: 'Number of results to return',
            default: 1,
          },
        },
      },
    },
  • src/index.ts:803-818 (registration)
    The registration/dispatch case in the CallToolRequestSchema handler that calls the listProjects function and returns the JSON response as text content.
    case 'list_projects': {
      const number_of_results = Number(
        request.params.arguments?.number_of_results ?? 1,
      );
    
      const response = await listProjects(number_of_results);
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(response, null, 2),
          },
        ],
      };
    }
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 mentions the API endpoint but doesn't disclose behavioral traits like pagination, rate limits, authentication needs, or what 'list all' entails (e.g., if it returns all projects at once or supports filtering). The markdown warning is minor and doesn't cover core behavior.

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?

Two sentences that are reasonably efficient, though the second sentence about markdown feels slightly out of place as it's more of a technical implementation note rather than core description. Overall, it's front-loaded with 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?

Given no annotations and no output schema, the description is incomplete. It lacks details on return format (e.g., what fields are included), error handling, or how 'list all' interacts with the 'number_of_results' parameter. For a read operation with one parameter, more context is needed.

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 parameter 'number_of_results' is fully documented in the schema. The description doesn't add any parameter-specific information beyond what the schema provides, maintaining the baseline score of 3.

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 action ('List all the projects') and target resource ('on Jira'), with specific API endpoint reference. However, it doesn't differentiate from sibling tools like 'execute_jql' or 'get_only_ticket_name_and_description' that might also retrieve project-related data, missing explicit distinction.

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 on when to use this tool versus alternatives like 'execute_jql' for filtered queries or other sibling tools. The description includes a technical note about not using markdown, but this doesn't help with tool selection context or prerequisites.

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/KS-GEN-AI/jira-mcp-server'

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