Skip to main content
Glama

gitlab_search_in_project

Search within a specific GitLab project to find issues, merge requests, code, commits, or wiki pages by specifying a search scope and query.

Instructions

Search within a project Returns: Results from specified scope Use when: Finding issues, MRs, code, wiki pages Required: Scope (what to search in)

Scopes:

  • 'issues': Search issue titles/descriptions

  • 'merge_requests': Search MR titles/descriptions

  • 'commits': Search commit messages

  • 'blobs': Search file contents

  • 'wiki_blobs': Search wiki pages

Example: Search for "login" in issues Returns matching issues with highlights

Related tools:

  • gitlab_search_projects: Search across projects

  • Specific list tools for each type

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idNoProject identifier (auto-detected if not provided) Type: integer OR string Format: numeric ID or 'namespace/project' Optional: Yes - auto-detects from current git repository Examples: - 12345 (numeric ID) - 'gitlab-org/gitlab' (namespace/project path) - 'my-group/my-subgroup/my-project' (nested groups) Note: If in a git repo with GitLab remote, this can be omitted
scopeYesSearch scope Type: string (enum) Options: - 'issues': Search in issues - 'merge_requests': Search in MRs - 'milestones': Search in milestones - 'wiki_blobs': Search in wiki pages - 'commits': Search in commit messages - 'blobs': Search in file contents - 'users': Search for users Required: Yes Example: 'issues' to find issues mentioning a term
searchYesSearch query Type: string Matching: Case-insensitive, partial matching Searches in: Project names and descriptions Examples: - 'frontend' (finds 'frontend-app', 'old-frontend', etc.) - 'API' (matches 'api', 'API', 'GraphQL-API', etc.) Tip: Use specific terms for better results
per_pageNoNumber of results per page Type: integer Range: 1-100 Default: 20 Example: 50 (for faster browsing) Tip: Use smaller values (10-20) for detailed operations, larger (50-100) for listing
pageNoPage number for pagination Type: integer Range: ≥1 Default: 1 Example: 3 (to get the third page of results) Note: Use with per_page to navigate large result sets
Behavior3/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 mentions what the tool returns ('Results from specified scope', 'Returns matching issues with highlights') and provides an example, but doesn't cover important behavioral aspects like authentication requirements, rate limits, error conditions, or pagination behavior (though pagination parameters exist in the schema). The description adds some context but leaves gaps for a search operation.

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 well-structured with clear sections (purpose, returns, use when, required, scopes, example, related tools) and every sentence earns its place. It's appropriately sized for a search tool with multiple scopes and provides essential information without redundancy.

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

Completeness4/5

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

For a search tool with 5 parameters, 100% schema coverage, and no output schema, the description provides good contextual completeness. It covers purpose, usage guidelines, scope options, and relationships to other tools. The main gap is the lack of output format details (no output schema exists), but the description mentions what gets returned ('Results from specified scope', 'Returns matching issues with highlights').

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 schema already fully documents all 5 parameters. The description adds minimal value beyond the schema - it mentions 'Required: Scope (what to search in)' and lists scopes, but the schema already provides this information with more detail. The description doesn't add meaningful parameter semantics beyond what's in the comprehensive schema descriptions.

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?

The description clearly states the specific action ('Search within a project') and resource ('project'), distinguishing it from sibling tools like 'gitlab_search_projects' (across projects) and specific list tools for each type. The opening line 'Search within a project' provides immediate clarity about scope and function.

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

Usage Guidelines5/5

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

The description explicitly states 'Use when: Finding issues, MRs, code, wiki pages' and provides a 'Related tools' section that names the alternative 'gitlab_search_projects' for cross-project searching. This gives clear guidance on when to use this tool versus its sibling alternatives.

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/Vijay-Duke/mcp-gitlab'

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