Gemini API tooling updates: context circulation, tool combos and Maps grounding for Gemini 3
Key Points
- Combine built-in tools and custom functions in one request
- Context circulation preserves and shares tool outputs
- Grounding with Google Maps added for Gemini 3
Summary
Google DeepMind updated the Gemini API to simplify building agentic, multi-tool workflows. Developers can now pass built-in tools (e.g., Google Search, Google Maps) and custom functions in a single request, circulate tool outputs across calls and turns, and use unique tool-call identifiers for reliable mapping and debugging. Grounding with Google Maps is now supported for the Gemini 3 model family. The Interactions API is recommended for stateful, multi-step workflows to leverage server-side state and unified reasoning traces.
Key Points
- Combine built-in tools and custom functions in the same Gemini API request to reduce orchestration complexity and end-to-end latency.
- Context circulation preserves every tool call and response in the model context so later steps (or other tools) can use previous outputs.
- Each tool call now includes a unique
idto map model-requested calls to client responses, improving debuggability and parallel call handling. - Grounding with Google Maps is available for the Gemini 3 family, giving access to spatial data, place details, commute times and local business info.
- Use the Interactions API for stateful multi-step flows to benefit from server-side state management and unified reasoning traces.
Practical tips for engineers
- Pass built-in tools (Search, Maps) alongside your function declarations in the same request rather than split orchestration steps.
- Persist and reference tool-call
idvalues when executing tools asynchronously or in parallel to correlate responses to model requests. - Rely on context circulation to feed a tool’s output into another tool or function without manual plumbing of intermediate results.
- Prefer Interactions API for complex agent workflows that need server-side state, traceability, and lower orchestration overhead.