Google Launches Tool Retrieval in Gemini API to Optimize Large-Scale Agent Performance
Google previews Tool Retrieval in the Gemini API, enabling agents to load tool schemas on demand to reduce input tokens and improve selection accuracy for large tool libraries.
On November 19, 2026, Google announced the preview launch of "Tool Retrieval" within the Interactions API of the Gemini API. This update aims to address the context bloat problem faced by AI agents when connecting to dozens or even hundreds of tools. In traditional setups, developers must send the full parameter schema for every tool in each request, which inflates input token counts, adds latency, and lowers tool-selection accuracy as the candidate list grows.
By enabling Tool Retrieval, an agent can keep its full tool library on standby and load parameter schemas only when the current task requires them. Developers simply add a tool_search tool to their request and set defer_loading: true for the tools they wish to hold back. The model still sees the name and description of every deferred tool, so it knows what is available, but the detailed parameter definitions stay out of the initial context window. When the model decides to use a tool, the API loads its full schema within the same request cycle, allowing the model to emit the function call normally.
This mechanism requires no index building or hosting from the developer; the search runs server-side on Gemini's infrastructure. For teams maintaining their own tool registries or permission filters, Google also offers a client-side retrieval mode where the application executes the search logic, though this adds one round trip per search. Additionally, Tool Retrieval is compatible with remote MCP (Model Context Protocol) servers, allowing entire servers' toolsets to be deferred at once.
Regarding pricing, Tool Retrieval incurs no separate charge; input and output tokens are billed at standard rates. While enabling tool_search adds a small fixed block of input tokens, and loaded schemas continue to be billed for the rest of the conversation, the savings from never loading unused schemas typically outweigh these costs for large libraries. The feature currently supports Gemini 3.6 and later models, including all Gemini 4 series models.