discuss.ai.google.dev
General feedback for Gemini API - Google AI Developers Forum
- The need for `alt=sse` in `streamGenerateContent` is very surprising, only documented as a side effect in the Shell example - No actual response body examples are presented for the shell examples - Tools are documented on separate pages, the first click through provides schema but does not provide examples (Caching | Gemini API | Google AI for Developers which is linked vs Intro to function calling with the Gemini API | Google AI for Developers which is also linked) … - Tool calls changing rules was somewhat confusing in experimental versions, rule changes should be documented: Gemini Pro Experimental 0801 is refusing to run functions - #11 by Sam_Saffron - The API overall is quite verbose and nested, it makes it harder to implement compared to anthropic / open ai Anyone else got feedback? Other feedback I saw here is: - [Feedback] Focus on Developers First - Safety settings are a surprise, especially compared to other vendors Also, @Sam_Saffron, there is no single, unified documentation that is straightforward and easy to follow. The current documentation is scattered across various channels. Search_Results3136×1314 390 KB
Related Pain Points3件
Scattered and Incomplete Gemini API Documentation
6The Gemini API documentation is fragmented across multiple pages with inconsistent examples, missing response body examples, and undocumented requirements (e.g., alt=sse parameter). Tools documentation lacks practical examples, and unified guidance is absent.
Gemini API Verbose and Complex Implementation
5The Gemini API is significantly more verbose and nested compared to competing APIs (Anthropic, OpenAI), making implementation more difficult and time-consuming. The overall design is developer-unfriendly compared to alternatives.
Undocumented Safety Settings Surprise
4Safety settings in the Gemini API have unexpected behavior and are inadequately documented compared to other vendors, causing confusion during implementation.