Hi ClickUp team,

I’m using the ClickUp MCP server via mcp-remote (https://mcp.clickup.com/mcp). It works great with some model providers, but when using Google/Gemini function calling, the MCP connection fails because one tool’s JSON Schema is rejected.

Specifically, clickup_get_workspace_hierarchy defines:

max_depth: { "type": "number", "enum": [0, 1, 2] }

Gemini appears to reject enum on non-string types, so the entire tool registration fails and my agent can’t run any commands once the ClickUp MCP tools are loaded.

Would you be able to adjust that input schema to be more broadly compatible? For example:

make max_depth a string enum ("type":"string","enum":["0","1","2"]) and coerce server-side, or

remove the enum and validate the allowed values on the server.

Happy to share more logs if helpful. Thanks!

— James Hereford