Skip to main content
Glama

Gemini Deep Research

gemini_deep_research

Performs multi-step live web search to investigate complex research questions. Returns a synthesised report with citations.

Instructions

Conduct real Deep Research on complex topics: Google's autonomous Deep Research agent does multi-step live web search and returns a synthesised, cited report (takes several minutes). Runs the actual Deep Research agents via the Gemini Interactions API. [MCP_RECOMMENDED_TIMEOUT_MS: 900000]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
research_questionYesThe complex research question or topic to investigate deeply
modelNoDeep Research agent to use: "deep-research-pro-preview-12-2025" (default), "deep-research-preview-04-2026", or "deep-research-max-preview-04-2026" (most thorough/slowest).
focus_areasNoOptional: specific areas to focus the research on

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYes
successYes
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Despite no annotations, the description discloses key behaviors: autonomous, multi-step live web search, synthesized cited report, takes several minutes, and includes a recommended timeout. This gives sufficient transparency for an AI agent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with two sentences, front-loading the purpose, and includes a valuable timeout hint. No unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex tool with an output schema, the description provides good context: behavior and API usage. It could mention the exact output format but is largely complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so each parameter is already described in the schema. The description does not add significant extra meaning beyond what's in the schema fields. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it conducts 'real Deep Research' using Google's autonomous agent, distinguishing it from sibling tools like chat or image analysis. The verb 'conducts' and resource 'Deep Research' are specific and informative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use for complex topics requiring multi-step web search and takes minutes, but does not explicitly state when not to use or name alternatives. It provides clear context but lacks exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Raindancer118/gemini-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server