Google Deepmind Upgrades Gemini API with Multi-Tool Chaining and Context Circulation

Google Deepmind has expanded the Gemini API with several developer-focused features designed to simplify complex workflows. The core upgrade enables multi-tool chaining, allowing built-in tools like Google Search and Google Maps to be combined with custom functions in a single API request.

What Changed

Previously, developers working with multiple tools had to orchestrate each step separately, requiring sequential API calls and manual result handling between steps. The new system automates this process through context circulation—results from one tool are automatically passed as input to the next tool in the chain.

Google has also introduced unique IDs for each tool call, improving debugging and error tracking capabilities. This makes it easier for developers to trace execution paths and identify which specific tool invocations caused issues in complex workflows.

Google Maps Integration

Google Maps is now available as a data source for the Gemini 3 model family. The integration provides access to location data, business information, and commute times, expanding the types of real-world information Gemini can incorporate into responses.

Implementation Path

Google recommends using the new Interactions API for building these multi-tool workflows. The company has not disclosed specific pricing changes or availability windows for these features.

What This Means

This update addresses a legitimate friction point for developers building agent-based applications. Multi-tool chaining with automatic context passing reduces boilerplate code and latency compared to sequential API calls. However, the practical impact depends on how broadly these tools are available (whether custom tools can truly integrate seamlessly with Google's built-in tools) and pricing implications for tool calls. The addition of Maps data to Gemini 3 is incremental—most competing models already support location-aware responses through various mechanisms. Developers using Gemini will likely find this useful for reducing implementation complexity, but this is a refinement rather than a fundamental capability shift.