gitlab-api

Get project jobs

gitlab_get_project_jobs

Read-onlyIdempotent

Retrieve GitLab CI/CD jobs for a specific project, with optional filters such as pipeline, scope, and pagination, to inspect job status and details.

Instructions

Get jobs associated with a specific project.

Args: **kwargs: Additional parameters for the request (e.g., project_id).

Returns: Response: A wrapper containing the original response and a list of Job models.

Raises: MissingParameterError: If the project_id is missing. ParameterError: If invalid parameters are provided.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gitlab_get_project_jobs"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No
`scope`	No
`job_id`	No
`per_page`	No
`max_pages`	No
`project_id`	No
`pipeline_id`	No
`total_pages`	No
`include_retried`	No
`job_variable_attributes`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv27.3.20Nov 7, 2026

removedInput schema / properties / api_parameters

Removed value: -{
-  "anyOf": [
-    {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null
-}

First observedv27.3.13Oct 25, 2026

TDQS

C2.8/5.0

Behavior3/5

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

Annotations already cover the read-only, idempotent, non-destructive, open-world safety profile. The description adds useful return and error context, including that project_id is effectively required despite the schema marking no required parameters, but it omits pagination behavior and filter semantics for a 10-parameter tool.

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

Conciseness3/5

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

The description is short and mostly front-loaded, but the Args section uses a misleading **kwargs placeholder instead of documenting the actual parameters, and the Returns/Raises boilerplate adds limited value compared with the missing usage and parameter details.

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 tool with 10 undocumented parameters, no output schema, and multiple similar siblings, the description is not complete enough. It does not explain filtering, pagination, or how this listing differs from related job-retrieval tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must explain parameters, but it only mentions project_id as an example under **kwargs. It says nothing about page, per_page, scope, pipeline_id, job_id, include_retried, or the pagination bounds, leaving most parameters opaque.

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 states a clear verb and resource: get jobs associated with a specific project. However, it does not distinguish this listing tool from siblings such as gitlab_get_pipeline_jobs, gitlab_get_project_job, or gitlab_get_runner_jobs, so the agent must infer the scope difference.

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?

There is no guidance on when to use this tool versus alternatives, nor on prerequisites beyond an error note about project_id. The description does not explain whether it lists all jobs in a project, filters by pipeline, or supports scoped retrieval.

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

Deploy Server