Skip to main content
Glama

gitlab_list_project_issues

Retrieve issues from a GitLab project to track development progress. Filter by state to view opened, closed, or all issues for project management.

Instructions

Lists issues in a GitLab project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectPathYesThe path of the GitLab project.
stateNoFilter issues by state.

Implementation Reference

  • Core handler function that executes the GitLab API call to list issues for a project, optionally filtered by state.
    // New tool: List Project Issues
    async listProjectIssues(projectPath: string, state?: 'opened' | 'closed' | 'all'): Promise<any[]> {
      const encodedProjectPath = encodeURIComponent(projectPath);
      let endpoint = `projects/${encodedProjectPath}/issues`;
      if (state) {
        endpoint += `?state=${state}`;
      }
      return this.callGitLabApi<any[]>(endpoint);
    }
  • src/index.ts:828-846 (registration)
    Tool registration in the MCP server's allTools array, including name, description, and input schema.
    {
      name: 'gitlab_list_project_issues',
      description: 'Lists issues in a GitLab project.',
      inputSchema: {
        type: 'object',
        properties: {
          projectPath: {
            type: 'string',
            description: 'The path of the GitLab project.',
          },
          state: {
            type: 'string',
            enum: ['opened', 'closed', 'all'],
            description: 'Filter issues by state.',
          },
        },
        required: ['projectPath'],
      },
    },
  • MCP server request handler that processes tool calls for gitlab_list_project_issues and delegates to GitLabService.
    case 'gitlab_list_project_issues': {
      if (!gitlabService) {
        throw new Error('GitLab service is not initialized.');
      }
      const { projectPath, state } = args as { projectPath: string; state?: 'opened' | 'closed' | 'all' };
      const result = await gitlabService.listProjectIssues(projectPath, state);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool lists issues but doesn't describe key behaviors: whether it requires authentication, returns paginated results, includes all issue fields or a subset, or has rate limits. For a read operation with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves in practice.

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 wasted words. It's front-loaded with the core purpose ('Lists issues in a GitLab project'), making it immediately scannable. Every word earns its place, and there's no redundancy or unnecessary elaboration.

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 moderate complexity (listing issues with filtering), lack of annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects (e.g., pagination, authentication needs) or output format (e.g., what fields are returned). For a tool with two parameters and no structured output documentation, the description should provide more context to be fully helpful.

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, clearly documenting both parameters ('projectPath' and 'state' with enum values). The description adds no parameter-specific information beyond what's in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even without param details in the description, which applies here.

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 ('Lists') and resource ('issues in a GitLab project'), making the purpose immediately understandable. It distinguishes this tool from siblings like 'gitlab_get_issue_details' (which retrieves a single issue) and 'gitlab_create_issue' (which creates issues). However, it doesn't specify the scope (e.g., all issues vs. filtered) or differentiate from 'gitlab_list_all_projects' (which lists projects, not issues).

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 doesn't mention when to choose it over 'gitlab_get_issue_details' for specific issues or 'gitlab_list_all_projects' for project-level operations. There's no context about prerequisites (e.g., needing project access) or typical use cases (e.g., triaging open issues).

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/HainanZhao/mcp-gitlab-jira'

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