Skip to main content
Glama
Google Workspace (GWS) MCP Server

Google Workspace (GWS) MCP Server

drive_files_export

Read-only

Converts Google Workspace Docs, Sheets, or Slides to a chosen format and returns JSON export metadata, so you can download or process files in the needed format.

Instructions

Export a Google Workspace file (Doc, Sheet, Slide) to a specific format. Returns JSON with export metadata. Use drive_files_download for automatic export with content returned inline.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "fileId": "<fileId>",
      "mimeType": "<mimeType>"
    },
    "name": "drive_files_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileIdYesThe Google Workspace file ID to export
mimeTypeYesExport format: text/plain, text/csv, application/pdf, application/vnd.openxmlformats-officedocument.wordprocessingml.document (docx), application/vnd.openxmlformats-officedocument.spreadsheetml.sheet (xlsx)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds only that it returns JSON with export metadata, which is vague — it does not clarify whether a download URL, base64 content, or just a descriptor comes back, nor error behavior for unsupported formats or non-Workspace fileIds.

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?

Three short sentences, purpose first, then the return shape, then the disambiguation. Zero redundant wording and the key sibling routing is not buried.

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

Completeness3/5

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

With no output schema, the description must explain the return value, and 'JSON with export metadata' is too thin to tell an agent whether the exported bytes or a link are available. The format-restriction note helps, but an agent still cannot predict what it will receive after the call.

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 both fileId and mimeType are already documented with accepted format examples. The description's only addition is narrowing the input to Docs/Sheets/Slides, which the schema does not say. Baseline 3 applies since the schema carries the semantics.

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?

States a specific verb and resource ('Export a Google Workspace file (Doc, Sheet, Slide) to a specific format') and immediately distinguishes itself from the closest sibling by naming drive_files_download. An agent can choose between them without opening either schema.

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?

Gives a clear routing rule: use drive_files_download when you want automatic export with content returned inline, implying this tool is for explicit mimeType control. It stops short of stating the inverse condition explicitly (when not to use the other tool) or what happens with non-exportable file types.

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