Gemini CLI v0.1.13: Issues with Schema for InputSchema

[tanaikech]

Gemini CLI has been updated from v0.1.12 to v0.1.13. This update appears to have changed the inputSchema expected for inputting arguments to the MCP server. Unfortunately, the current version (v0.1.13) does not seem to support JSON schema for inputSchema.

For instance, with get_values_from_google_sheets, I previously used the following schema. This schema worked correctly until v0.1.12, and my testing confirmed that only this tool was affected by the change.

{
  name: "get_values_from_google_sheets",
  description: "Use this to get cell values from Google Sheets.",
  inputSchema: {
    type: "object",
    properties: {
      spreadsheetId: { type: "string", description: "Spreadsheet ID of Google Sheets." },
      spreadsheetUrl: { type: "string", description: "Spreadsheet URL of Google Sheets." },
      sheetName: { type: "string", description: "Sheet name in the Google Sheets. If both sheetName, sheetId, and sheetIndex are not provided, the values are retrieved from the 1st sheet on Google Sheets." },
      sheetId: { type: "string", description: "Sheet ID of the sheet in Google Sheets. If both sheetName, sheetId, and sheetIndex are not provided, the values are retrieved from the 1st sheet on Google Sheets." },
      sheetIndex: { type: "number", description: "Sheet index (The 1st sheet is 0.) of the sheet in Google Sheets. If both sheetName, sheetId, and sheetIndex are not provided, the values are retrieved from the 1st sheet on Google Sheets." },
      range: { type: "string", description: "Range as A1Notation. The values are retrieved from this range. If this is not used, the data range is automatically used." },
    },
    oneOf: [{ required: ["spreadsheetId"] }, { required: ["spreadsheetUrl"] }]
  }
}

However, after updating Gemini CLI to v0.1.13, using the above tool results in the following error:

✕ [API Error: {"error":{"message":"{\n  \"error\": {\n    \"code\": 400,\n    \"message\": \"schema at anyOf.0 requires unspecified property 'spreadsheetId'\",\n    \"status\": \"INVALID_ARGUMENT\"\n  }\n}\n","code":400,"status":"Bad Request"}}]

This error message, specifically "schema at anyOf.0 requires unspecified property 'spreadsheetId'," is confusing because my schema uses oneOf, not anyOf.

Even when I modify oneOf to anyOf, the same error occurs.

For example, when I modify oneOf: [{ required: ["spreadsheetId"] }, { required: ["spreadsheetUrl"] }] to required: ["spreadsheetId"], no error occurs, and the tool works fine.

Given this unexpected behavior, and the uncertainty about whether this change in v0.1.13 is a permanent specification, I am hesitant to update my MCP server tools. Therefore, I am currently continuing to use Gemini CLI v0.1.12.

It's also worth noting that v0.1.13 no longer supports complex schemas that were compatible with v0.1.12. Ref

[wanlin31]

Hello @tanaikech thank you for surfacing the issue.

The error you see in the description is from our backend, we treated the oneOf as anyOf when there isn't anyOf, so the error message is confusing. Sorry about that, we are working on fixing it.

We are investigating this issue on our end, thank you for the patience.

I saw you also mentioned: v0.1.13 no longer supports complex schemas that were compatible with v0.1.12., there are multiple tool mentioned in the reference, can you help identify which tool or tools exactly that doesn't work now?

Thank you.

[tanaikech]

Hello @wanlin31
Thank you for your reply; I'm glad you're looking into this issue.

I currently have 41 tools. When I tested them individually, I found that 9 out of 41 tools failed with v0.1.13, as shown in the table below. I've confirmed that all tools worked correctly with v0.1.12.

Failed tools	Error message
get_values_from_google_docs	schema at anyOf.0 requires unspecified property 'documentId'
put_values_into_google_docs	schema at anyOf.0 requires unspecified property 'documentId'
manage_google_docs_using_docs_api	reference to undefined schema at properties.requests.items
get_values_from_google_sheets	schema at anyOf.0 requires unspecified property 'spreadsheetId'
put_values_to_google_sheets	schema at anyOf.0 requires unspecified property 'spreadsheetId'
search_values_from_google_sheets	schema at anyOf.0 requires unspecified property 'spreadsheetId'
manage_google_sheets_using_sheets_api	reference to undefined schema at properties.requests.items
manage_google_slides_using_slides_api	reference to undefined schema at properties.requests.items
generate_roadmap_to_google_sheets	schema at anyOf.0 requires unspecified property 'spreadsheetId

For example, an error occurs if even just one of the tools listed above is included.

For future Gemini CLI updates, please let me know if the schema I am currently using will no longer be compatible so I can modify it. Ideally, I would prefer if the current schema could continue to be used. Many users currently use my tools, and I would like to continue updating them for the Gemini CLI.

[tanaikech]

@wanlin31 I had updated ToolsForMCPServer to use with v0.1.13 by updating the schema. But when I updated Gemini CLI from v0.1.13 to v0.1.14, I confirmed that the previous schema could be used. So, I reimplemented the previous schema. By this, the request body for APIs can be directly generated using Gemini CLI v0.1.14. Thank you so much!

So, I will close this issue.

[wanlin31]

@tanaikech Thank you for confirming, we really appreciate it!