Skip to main content
Glama

gitlab_get_user_resolved_issues

Retrieve issues closed or resolved by a specific user to track problem-solving contributions, analyze team productivity, and build knowledge bases for performance reviews.

Instructions

Get issues closed/resolved by a user

Find all issues that were closed or resolved by the specified user, showing their problem-solving contributions and impact.

Returns resolved issues with:

  • Issue details: original problem, resolution

  • Resolution info: how it was closed, related MRs

  • Timeline: resolution time, effort indicators

  • Impact: complexity, stakeholders affected

  • Recognition: contribution to project health

Use cases:

  • Track problem resolution contributions

  • Performance reviews and recognition

  • Knowledge base building

  • Team productivity analysis

Parameters:

  • user_id: Numeric user ID

  • username: Username string (use either user_id or username)

  • since: Resolved after date (YYYY-MM-DD)

  • until: Resolved before date (YYYY-MM-DD)

  • complexity: Filter by resolution complexity

  • sort: Sort order (closed, complexity, impact)

  • per_page: Results per page (default: 20)

  • page: Page number (default: 1)

Example: Get issues resolved this quarter

{
  "username": "johndoe",
  "since": "2024-01-01",
  "until": "2024-03-31",
  "sort": "closed"
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idNoNumeric user ID
usernameNoUsername string
sinceNoResolved after date (YYYY-MM-DD)
untilNoResolved before date (YYYY-MM-DD)
complexityNoFilter by resolution complexity
sortNoSort orderclosed
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

Implementation Reference

  • The handler function that executes the core logic of the tool: extracts parameters from arguments and calls the GitLabClient method to retrieve user's resolved issues.
    def handle_get_user_resolved_issues(client: GitLabClient, arguments: Optional[Dict[str, Any]]) -> Dict[str, Any]:
        """Handle getting user's resolved issues"""
        user_id = get_argument(arguments, "user_id")
        username = get_argument(arguments, "username")
        since = get_argument(arguments, "since")
        until = get_argument(arguments, "until")
        complexity = get_argument(arguments, "complexity")
        sort = get_argument(arguments, "sort", "closed")
        per_page = get_argument(arguments, "per_page", DEFAULT_PAGE_SIZE)
        page = get_argument(arguments, "page", 1)
        
        return client.get_user_resolved_issues(
            user_id=user_id,
            username=username,
            since=since,
            until=until,
            complexity=complexity,
            sort=sort,
            per_page=per_page,
            page=page
        )
  • MCP tool schema definition specifying input parameters, types, descriptions, and validation rules for the gitlab_get_user_resolved_issues tool.
    types.Tool(
        name=TOOL_GET_USER_RESOLVED_ISSUES,
        description=desc.DESC_GET_USER_RESOLVED_ISSUES,
        inputSchema={
            "type": "object",
            "properties": {
                "username": {"type": "string", "description": "Username string"},
                "since": {"type": "string", "description": "Issues resolved after date (YYYY-MM-DD)"},
                "until": {"type": "string", "description": "Issues resolved before date (YYYY-MM-DD)"},
                "per_page": {"type": "integer", "description": desc.DESC_PER_PAGE, "default": DEFAULT_PAGE_SIZE, "minimum": 1, "maximum": MAX_PAGE_SIZE},
                "page": {"type": "integer", "description": desc.DESC_PAGE_NUMBER, "default": 1, "minimum": 1}
            },
            "required": ["username"]
        }
    ),
  • Maps the tool name to its handler function in the TOOL_HANDLERS dictionary, which is used by the MCP server to dispatch calls to the correct handler.
    TOOL_GET_USER_RESOLVED_ISSUES: handle_get_user_resolved_issues,
  • Constant defining the exact tool name string used throughout the codebase for consistency.
    TOOL_GET_USER_RESOLVED_ISSUES = "gitlab_get_user_resolved_issues"
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. It discloses that the tool returns resolved issues with details like 'Issue details', 'Resolution info', and 'Timeline', which adds behavioral context beyond basic retrieval. However, it lacks information on permissions, rate limits, or error handling, leaving gaps for a tool with 8 parameters and no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with sections like 'Returns resolved issues with:', 'Use cases:', 'Parameters:', and an example, making it easy to scan. However, some details in the 'Returns' section (e.g., 'Recognition: contribution to project health') are somewhat verbose and could be trimmed for better conciseness.

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 complexity (8 parameters, no annotations, no output schema), the description is moderately complete. It covers purpose, usage, and parameters but lacks details on output format, pagination behavior (beyond listing parameters), and error cases. This is adequate but has clear gaps for a tool with this level of complexity.

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 documents all parameters thoroughly. The description lists parameters with brief notes (e.g., 'use either user_id or username'), adding minimal value beyond the schema. This meets the baseline of 3, as the schema does the heavy lifting.

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 ('Get issues closed/resolved by a user') and resource ('issues'), distinguishing it from sibling tools like 'gitlab_get_user_open_issues' or 'gitlab_list_issues' by focusing on resolved issues rather than open ones or general listings. The title 'Get issues closed/resolved by a user' reinforces this specificity.

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?

The description provides clear context with 'Use cases' (e.g., 'Track problem resolution contributions', 'Performance reviews'), which implicitly guides when to use this tool. However, it does not explicitly state when not to use it or name alternatives (e.g., 'gitlab_get_user_open_issues' for unresolved issues), missing full explicit guidance.

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