Skip to main content
Glama
nabheet

google-services-mcp

by nabheet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Export Drive file

google_drive_export

Export Google-native Docs, Sheets, Slides, or Drawings to formats such as PDF or DOCX; optionally write the exported bytes to a local file path.

Instructions

Export a Google-native file (Docs/Sheets/Slides/Drawings) to another format (e.g. application/pdf, text/plain, application/vnd.openxmlformats-officedocument.wordprocessingml.document). Pass saveToPath to write the exported bytes to a local file instead.

Input Schema

NameRequiredDescriptionDefault
fileIdYesDrive file ID.
accountNoAccount nickname to use.
mimeTypeYesTarget MIME type (e.g. application/pdf).
saveToPathNoLocal path to write the exported bytes to (returns { savedTo }). Must be inside the save root: GOOGLE_MCP_SAVE_ROOT, default ~/Downloads.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.95
    • addedInput schema / properties / saveToPath
      Added value: +{
+  "description": "Local path to write the exported bytes to (returns { savedTo }). Must be inside the save root: GOOGLE_MCP_SAVE_ROOT, default ~/Downloads.",
+  "type": "string"
+}
  2. Addedv0.1.30

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load. It discloses the destination behavior and mentions the { savedTo } return shape, but says nothing about auth requirements, the roughly 10MB Drive export size limit, whether the source file is modified, or error behavior on unsupported MIME conversions.

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?

Two sentences, zero padding, with the capability and its file-type scope front-loaded before the optional output-routing behavior. Every sentence carries information.

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 4-param tool with full schema coverage and no output schema, the description covers what it does, what it accepts, and the two output modes. It falls short only on operational limits and MIME-compatibility caveats that an agent might need to avoid failed calls.

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 the schema already documents all four parameters including the save-root constraint. The description only restates mimeType examples and saveToPath's purpose, adding no format rules or validation details beyond the schema.

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

Purpose4/5

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

States a specific verb+resource with an explicit scope restriction (Google-native Docs/Sheets/Slides/Drawings only), which effectively separates it from google_drive_download for binary files. It does not name the sibling outright, so the differentiation is inferred rather than declared.

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 clear applicability context: only Google-native files can be exported, and passing saveToPath switches from returning bytes to writing a local file. No explicit when-not-to-use or named alternative (e.g. 'for non-native binary files use google_drive_download') is provided.

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

Deploy Server

Other Tools