Skip to main content
Glama
machinemates-ai

Gemini Research MCP Server

resume_research

Read-only

Resume interrupted deep research sessions. List recoverable sessions or check a specific session's status to retrieve the completed report.

Instructions

Resume an interrupted or in-progress research_deep session.

Use when a research_deep call was cut short (client disconnect, transport error, cancellation) or when you want to check whether a long-running session has since completed on Gemini's servers.

Because research_deep persists its session at the start, the research continues on Gemini's side even when the MCP client goes away — this tool retrieves the result once it's ready.

Call with no arguments to list recoverable sessions. Call with an interaction_id (returned by the original research_deep call or by list_research_sessions) to check a specific session's status; if it has completed, the full report is returned. Hand the result off to export_research_session(format="docx") to save the report to disk.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
interaction_idNoOptional: specific interaction_id to resume. If not provided, shows resumable sessions.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations declare readOnlyHint and openWorldHint. Description adds context: research continues on Gemini's side even if client disconnects, and result is returned once ready. No contradictions with annotations.

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

Conciseness4/5

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

Description is well-structured with clear paragraphs. Each sentence adds value. Slightly verbose but efficiently conveys all necessary information without redundancy.

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

Completeness5/5

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

Given the presence of an output schema, the description covers behavioral aspects, error scenarios (disconnect, cancellation), and usage flow (hand off to export). No gaps for this tool's complexity.

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

Parameters4/5

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

Schema already describes parameter well (100% coverage). Description adds value by explaining the two modes of operation: no argument lists sessions, with interaction_id checks status. Goes beyond schema's description.

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 the tool resumes an interrupted 'research_deep' session. It uses specific verb 'resume' and resource 'research_deep session', and distinguishes from siblings like 'research_web' and 'research_deep' by targeting interrupted sessions only.

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?

Explicitly describes when to use: when a 'research_deep' call was cut short or to check session completion. Provides behavior for no arguments (list sessions) and with interaction_id (check status). Mentions alternative export tool. Missing explicit when-not-use, but context and sibling names cover that.

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/machinemates-ai/gemini-research-mcp'

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