Skip to main content
Glama

search_issues

Search for issues in a GitLab project using filters like state, labels, and keywords to find relevant tickets and track project tasks.

Instructions

Search for issues in a GitLab project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesProject ID or URL-encoded path
searchYesSearch term for title and description
stateNoFilter issues by state
labelsNoComma-separated list of label names
pageNoPage number for pagination (default: 1)
per_pageNoNumber of results per page (default: 20)

Implementation Reference

  • Implementation of the search_issues tool handler.
    export async function searchIssues(
      projectId: string,
      searchTerm: string,
      options: {
        state?: "opened" | "closed" | "all";
        labels?: string;
        page?: number;
        per_page?: number;
      } = {}
    ): Promise<GitLabIssue[]> {
      if (!searchTerm?.trim()) {
        throw new Error("Search term is required");
      }
    
      return listIssues(projectId, {
        search: searchTerm,
        ...options
      });
    }
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. While 'Search' implies a read operation, the description doesn't address important behavioral aspects like authentication requirements, rate limits, pagination behavior beyond what's in the schema, error conditions, or what the return format looks like. This leaves significant gaps for an agent to understand how to properly interact with this tool.

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 communicates the core functionality without any wasted words. It's appropriately sized and front-loaded with the essential information, making it easy for an agent 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?

For a search tool with 6 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain what constitutes a successful search, what format results are returned in, how pagination works beyond the parameter definitions, or any error conditions. The agent would need to guess about many aspects of tool behavior.

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 schema description coverage is 100%, meaning all parameters are well-documented in the schema itself. The description doesn't add any meaningful parameter semantics beyond what's already in the schema fields. According to the scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no additional parameter information in the description.

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 ('Search for issues') and resource ('in a GitLab project'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'list_issues' or 'search_groups', which would require more specific scope or context information.

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 'list_issues' or 'search_groups'. There's no mention of prerequisites, appropriate contexts, or exclusions that would help an agent choose between similar tools in this server's toolset.

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/TheRealChrisThomas/gitlab-mcp-server'

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