Skip to main content
Glama

list_projects

Retrieve all accessible Jira projects to view available work items and project metadata for issue management and tracking.

Instructions

List all accessible Jira projects

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxResultsNoMaximum number of projects to return (default: 50)

Implementation Reference

  • The handler function that executes the list_projects tool by fetching projects from Jira API and formatting the response using JiraFormatters.
    async handleListProjects(args: any) {
      try {
        const { maxResults = 50 } = args || {};
    
        const params = {
          maxResults,
        };
    
        const projects = await this.apiClient.get('/project', params);
    
        return {
          content: [
            {
              type: 'text',
              text: JiraFormatters.formatProjects(projects),
            },
          ],
        };
      } catch (error: any) {
        return {
          content: [
            {
              type: 'text',
              text: JiraFormatters.formatError(error),
            },
          ],
          isError: true,
        };
      }
    }
  • The tool definition including name, description, and input schema for the list_projects tool.
    {
      name: 'list_projects',
      description: 'List all accessible Jira projects',
      inputSchema: {
        type: 'object',
        properties: {
          maxResults: {
            type: 'number',
            description: 'Maximum number of projects to return (default: 50)',
          },
        },
      },
    },
  • src/index.ts:110-111 (registration)
    The switch statement case that registers and dispatches list_projects tool calls to the projectHandlers.handleListProjects method.
    case 'list_projects':
      return this.projectHandlers.handleListProjects(request.params.arguments);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions 'accessible' projects, hinting at permission constraints, but doesn't specify authentication requirements, rate limits, pagination behavior, or what 'accessible' means in practice. For a read operation with zero annotation coverage, this leaves significant gaps.

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 that directly states the tool's purpose without any unnecessary words. It's appropriately sized and front-loaded, making it easy to understand at a glance.

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 simplicity (one optional parameter, no output schema, no annotations), the description is minimally adequate. However, it lacks information about return format, pagination, or error handling that would be helpful for a list operation, especially with no output schema provided.

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 the single parameter 'maxResults' clearly documented in the schema. The description adds no additional parameter information beyond what's in the schema, so it meets the baseline score when schema coverage is high.

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') and resource ('accessible Jira projects'), making the tool's purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'search_issues' or 'get_issue' that also retrieve Jira data, so it doesn't reach the highest score.

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 like 'search_issues' or 'get_issue', nor does it mention any prerequisites or context for usage. It simply states what the tool does without indicating appropriate scenarios.

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

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