Skip to content

get_pipeline_jobs requires project_id parameter but error message is confusing

What I was doing

I was using the get_pipeline_jobs function to retrieve jobs for a specific pipeline during an automated npm package release process.

What I expected

I expected the function to either:

  1. Work with just the pipeline_id parameter, or
  2. Provide a clear error message indicating that project_id is required

What actually happened

I received this confusing error:

MCP error -32603: Invalid arguments: project_id: Invalid input

The error message suggests that project_id was provided but was invalid, when in reality I had omitted the project_id parameter entirely.

Repro steps

  1. Call get_pipeline_jobs with only the pipeline_id parameter: 
    get_pipeline_jobs(pipeline_id: 1053)
  2. Observe the error message

Expected vs Actual Error Message

  • Expected: "Missing required parameter: project_id" or "project_id is required"
  • Actual: "Invalid arguments: project_id: Invalid input" (implies project_id was provided but invalid)

Additional Context

  • The function worked correctly when I provided both parameters: get_pipeline_jobs(project_id: 5588, pipeline_id: 1053)
  • This occurred during a /publish-npm-package command execution
  • The confusing error message led to initial confusion about what was wrong

Environment

  • MCP Server: gitlab-git-haley-io (version unknown - please add version reporting)
  • Context: Automated npm package publishing workflow
  • Pipeline ID: 1053
  • Project ID: 5588

Suggested Fix

Improve the error message to clearly indicate when required parameters are missing vs when provided parameters are invalid.