API Error: 400 Invalid JSON Prevents File Read

[ypenn21]

What happened?

reproduce error by following :

1. Authenticated with gemini-api-key /auth
2. Set export GOOGLE_GENAI_API_VERSION=v1 # default is v1beta
3. The cli to read any file it returns an 400 error:

GOOGLE_GENAI_API_VERSION to v1 instead of the default for enterprise concern with v1beta being unstable..

What did you expect to happen?

The cli should parse the file, and continue with it's thought chain process.

Client information

Client Information

Run gemini to enter the interactive CLI, then run the /about command.

│ About Gemini CLI                                                                                                                                                                                              
│ CLI Version                                                             0.33.0                                                                                                                                │
│ Git Commit                                                              6ee19e1f6                                                                                                                             │
│ Model                                                                   Auto (Gemini 3)                                                                                                                       │
│ Sandbox                                                                 no sandbox                                                                                                                            │
│ OS                                                                      darwin                                                                                                                                │
│ Auth Method                                                             gemini-api-key                                                                                                                        │
│ GCP Project                                                             genai-apps-25                                                                                                                         │
│ IDE Client                                                              Antigravity        

Login information

API key

Anything else we need to know?

This doesn't happen with Google Account, or Vertexai auth.

[ypenn21]

I also get error with vertexai auth

when i set:

GOOGLE_GENAI_API_VERSION to v1

But the difference is the 400 happens on mcp tool usage. specifically jira in this case.

✕ [API Error: {"error":{"message":"{\n "error": {\n "code": 400,\n "message": "Invalid JSON
payload received. Unknown name \"id\" at 'contents[6].parts[0].function_response': Cannot find
field.",\n "status": "INVALID_ARGUMENT",\n "details": [\n {\n "@type":
"type.googleapis.com/google.rpc.BadRequest",\n "fieldViolations": [\n {\n
"field": "contents[6].parts[0].function_response",\n "description": "Invalid JSON
payload received. Unknown name \"id\" at 'contents[6].parts[0].function_response': Cannot find
field."\n }\n ]\n }\n ]\n }\n}\n","code":400,"status":"Bad Request"}}]

[ypenn21]

Any updates on when this will be shipped?

[gemini-cli]

File reading fails completely when using the v1 API endpoint due to a 400 error. Blocks file reading.

Effort Analysis:
The file reading tool constructs a payload that is rejected as a 400 error by the v1 Gemini API endpoint due to strict JSON validation differences compared to v1beta. The fix involves a localized adjustment to the tool's parameter formatting logic to ensure it complies with the v1 schema requirements. This is a straightforward schema compatibility fix and a localized bug fix, mapping cleanly to effort/small.