gitlab_list_project_jobs

List and filter project jobs across GitLab CI/CD pipelines for monitoring, troubleshooting, and job history review. Supports pagination and status-based scoping for efficient navigation.

Instructions

List all jobs for a project Returns: Array of jobs across all pipelines with filtering options Use when: Monitoring project CI/CD, finding recent failures, browsing job history Pagination: Yes (default 20 per page) Filtering: By job status/scope (failed, success, running, etc.)

Example response: [{ "id": 67890, "name": "deploy", "stage": "deploy", "status": "failed", "pipeline": {"id": 123, "ref": "main"}, "commit": {"short_id": "abc1234"}, "created_at": "2023-01-01T15:30:00Z", "user": {"name": "Jane Doe"} }]

Related tools:

gitlab_list_pipeline_jobs: Jobs for specific pipeline
gitlab_list_pipelines: Find pipeline information

Input Schema

Name	Required	Description
`page`	No	Page 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
`per_page`	No	Number 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
`project_id`	No	Project 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
`scope`	No	Job scope filter Type: string Format: Filter jobs by status Options: 'created' \| 'pending' \| 'running' \| 'failed' \| 'success' \| 'canceled' \| 'skipped' \| 'waiting_for_resource' \| 'manual' Examples: - 'failed' (only failed jobs) - 'success' (only successful jobs) - 'running' (currently running jobs)

Input Schema (JSON Schema)

{
  "properties": {
    "page": {
      "default": 1,
      "description": "Page number for pagination\nType: integer\nRange: ≥1\nDefault: 1\nExample: 3 (to get the third page of results)\nNote: Use with per_page to navigate large result sets",
      "minimum": 1,
      "type": "integer"
    },
    "per_page": {
      "default": 50,
      "description": "Number of results per page\nType: integer\nRange: 1-100\nDefault: 20\nExample: 50 (for faster browsing)\nTip: Use smaller values (10-20) for detailed operations, larger (50-100) for listing",
      "maximum": 100,
      "minimum": 1,
      "type": "integer"
    },
    "project_id": {
      "description": "Project identifier (auto-detected if not provided)\nType: integer OR string\nFormat: numeric ID or 'namespace/project'\nOptional: Yes - auto-detects from current git repository\nExamples:\n  - 12345 (numeric ID)\n  - 'gitlab-org/gitlab' (namespace/project path)\n  - 'my-group/my-subgroup/my-project' (nested groups)\nNote: If in a git repo with GitLab remote, this can be omitted",
      "type": "string"
    },
    "scope": {
      "description": "Job scope filter\nType: string\nFormat: Filter jobs by status\nOptions: 'created' | 'pending' | 'running' | 'failed' | 'success' | 'canceled' | 'skipped' | 'waiting_for_resource' | 'manual'\nExamples:\n  - 'failed' (only failed jobs)\n  - 'success' (only successful jobs)\n  - 'running' (currently running jobs)",
      "enum": [
        "created",
        "pending",
        "running",
        "failed",
        "success",
        "canceled",
        "skipped",
        "waiting_for_resource",
        "manual"
      ],
      "type": "string"
    }
  },
  "type": "object"
}

MCP GitLab Server