CERN GitLab MCP Server

search_issues

Read-only

Search CERN GitLab issues and discussions to understand library usage, find solutions to common errors, or verify feature support in High Energy Physics projects.

Instructions

Search for issues and discussions in CERN GitLab projects. Useful for understanding how a library is used, finding solution to common errors, or checking if a feature is supported.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`state`	No	Filter by issue state	all
`project`	No	Optional: limit search to a specific project. If omitted, searches across all projects you have access to.
`per_page`	No	Number of results to return
`search_term`	Yes	Keywords to search for in issue titles and descriptions

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedv0.3.0Aug 28, 2026
- addedInput schema / properties / per_page / default
```
Added value: +10
```
- changedInput schema / properties / per_page / description
```
Previous value: -"Number of results to return (default: 10, max: 100)"New value: +"Number of results to return"
```
- addedInput schema / properties / per_page / maximum
```
Added value: +100
```
- addedInput schema / properties / per_page / minimum
```
Added value: +1
```
- addedInput schema / properties / per_page / title
```
Added value: +"Per Page"
```
- addedInput schema / properties / project / default
```
Added value: +""
```
- addedInput schema / properties / project / title
```
Added value: +"Project"
```
- addedInput schema / properties / search_term / title
```
Added value: +"Search Term"
```
- addedInput schema / properties / state / default
```
Added value: +"all"
```
- changedInput schema / properties / state / description
```
Previous value: -"Filter by issue state (default: all)"New value: +"Filter by issue state"
```
- addedInput schema / properties / state / title
```
Added value: +"State"
```
- addedInput schema / title
```
Added value: +"search_issues_fnArguments"
```
- changedOutput schema / (root)
```
Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "search_issues_fnDictOutput",
+  "type": "object"
+}
```
First observedv0.1.6Mar 27, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds that the scope is issues/discussions rather than code and targets CERN GitLab projects. It doesn't mention default state, cross-project behavior, or pagination, though these are covered by the schema. No contradiction with annotations.

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?

Two sentences, with the core function stated first and practical use cases second. There is no filler and no repetition of schema fields or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only search tool with fully described parameters and an output schema, the description supplies the missing decision context: what kind of content is searched and when the tool is useful. Nothing necessary to call it correctly is missing.

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?

All four parameters have schema descriptions, so the schema carries the semantic weight and the baseline is 3. The description reinforces the purpose of search_term through use cases but adds no parameter-specific meaning beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Search') with a clear resource ('issues and discussions in CERN GitLab projects'). Differentiates from siblings like search_code and search_projects by naming the content type being searched.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides concrete use cases such as 'understanding how a library is used, finding solution to common errors, or checking if a feature is supported,' which tells an agent when this tool is appropriate. It doesn't explicitly name alternative tools or exclusion criteria, so it stops short of 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server