Skip to main content
Glama
machinemates-ai

Gemini Research MCP Server

by machinemates-ai
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

export_research_session

Read-onlyIdempotent

Export completed research sessions to Word, Markdown, or JSON files. Recover reports after deep research runs or convert them into shareable documents.

Instructions

Save (export, download, archive) a completed research session to a file on disk — Word (.docx), Markdown (.md), or JSON. Use this to recover your report after a research_deep run completes or is interrupted, and to convert reports into a shareable Word document.

Disk-first contract. The file is always written to disk, and the absolute path is returned on the first line of the response as Saved to: <path>. When output_path is omitted the file lands in GEMINI_RESEARCH_EXPORT_DIR (default ~/.gemini-research/exports/). An EmbeddedResource is still attached so GUI hosts can expose their native "Save As" affordance.

Similar to Google's Deep Research export feature, the DOCX output is a professional Word document suitable for sharing, archiving, or further editing.

Supported formats:

  • docx: Word document with headings, lists, and table of contents

  • markdown: Clean .md file with full report and citations

  • json: Machine-readable, all metadata preserved

Typical recovery flow:

  1. research_deep(...) completes (or is resumed via resume_research).

  2. export_research_session(format="docx") — no other arguments needed; the path on disk is returned in the response text.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoOptional: search for a session by query text instead of interaction_id
formatNoExport format: 'markdown' (.md), 'json' (.json), or 'docx' (Word document)markdown
output_pathNoFilesystem path to save the exported file to. Absolute or relative to the MCP server's working directory. If omitted, the file is automatically written to GEMINI_RESEARCH_EXPORT_DIR (default ~/.gemini-research/exports/) and the resolved path is returned in the response. Parent directory must already exist when an explicit path is supplied.
interaction_idNoInteraction ID of the session to export. If not provided, exports the most recent.

Tool Definition Quality

A3.9/5.0
Behavior1/5

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

The description thoroughly explains the disk-writing behavior and path handling, but it contradicts the readOnlyHint annotation (true), which implies no side effects. According to rules, a contradiction scores 1. The description is transparent but incompatible with the annotation.

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 well-structured with clear sections (purpose, disk-first contract, supported formats, typical flow). Each sentence adds unique value 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 no output schema, the description explains the return format (path on first line, EmbeddedResource). It covers all parameters and typical use cases, making the tool's behavior fully understandable.

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 description coverage is 100%, so baseline is 3. The description adds value by explaining default behavior for format, path resolution, and interaction_id selection (e.g., 'exports the most recent' if omitted). This justifies a slight above-baseline score.

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 action ('Save (export, download, archive)'), the resource ('completed research session'), and the output formats (docx, md, json). It also ties the tool to the research_deep workflow, distinguishing it from siblings like research_web and resume_research.

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 explicitly states when to use this tool: 'after a research_deep run completes or is interrupted' and provides a typical recovery flow. It does not explicitly mention when not to use it, but the context is clear and no alternative export tool exists among siblings.

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