Repository navigation
Gemini CLI v0.1.19: Issues with Schema for InputSchema #9
Description
I've reencountered a schema-related error after updating the Gemini CLI from v0.1.18 to v0.1.19. All 115 tools worked correctly in v0.1.18, but the update caused two distinct problems:
- When a schema containing a
$refis used, the CLI fails to launch with a "missing types in its parameter schema" error. - If I modify the same schema to remove the
$refand flatten it, a different error occurs: "FunctionDeclaration in the request exceeds the maximum allowed nesting depth" when running a prompt.
The following tools are affected:
classroom_courses_updateGradingPeriodSettingsclassroom_courses_students_createclassroom_courses_teachers_createclassroom_courses_courseWorkMaterials_createclassroom_courses_courseWorkMaterials_patchclassroom_courses_courseWork_studentSubmissions_patchclassroom_courses_courseWork_rubrics_createclassroom_courses_courseWork_rubrics_patchmanage_google_docs_using_docs_apimanage_google_sheets_using_sheets_apimanage_google_slides_using_slides_api
The original schema caused the nesting depth error, so I had introduced $ref as a workaround in v0.1.18, which was successful. The update seems to have broken this fix.
I've noticed an additional issue: the following tools can't be used. When I include them, running a prompt results in the error, "FunctionDeclaration in the request exceeds the maximum allowed nesting depth." This error didn't occur in version 0.1.18.
classroom_courses_announcements_createclassroom_courses_announcements_patch
Action Required: For now, please continue to use Gemini CLI v0.1.18 when working with these tools.
Future: I will track and confirm the status of the tool updates in parallel with the Gemini CLI update.
Note: About the error "FunctionDeclaration in the request exceeds the maximum allowed nesting depth.", today, when I downgrade from v0.1.19 to v0.1.18 and test it again, I noticed that the tools that worked yesterday didn't work with this error now. So, this might be due to the change in the specification at Gemini.
Activity
tanaikech commentedon Aug 13, 2025
I've dealt with this issue.
https://github.com/tanaikech/ToolsForMCPServer/releases/tag/v1.0.22
tanaikech commentedon Aug 14, 2025
I updated to v1.0.24.
I’ve dealt with an issue caused by the update of the Gemini CLI from v0.1.18 to v0.1.19.
The update has lowered the schema nesting depth, which now requires the use of
$ref. However, theparametersJsonSchemaappears to be incompatible with this. This means that a request body, such as thebatchUpdatefor the Docs, Sheets, and Slides APIs, cannot be directly generated using the input schema. It would be very useful if an AI agent could directly generate this type of complex request body.To solve this, I explored solutions to manage the low depth without using
$reffor these three tools. I came up with the following workaround:With this workaround, the input schema remains simple, and the complex JSON schema can still be used to generate the request body. Additionally, no errors occur when using the Gemini CLI.