Skip to main content
Glama

drive_import

Bring a file from the registered Google Drive folders into the workspace's files, where search, knowledge and files.read can use it. A Google Doc is stored as .docx, a Sheet as .xlsx, Slides as .pdf (up to 10 MB); any other file as it is. A file up to 50 MB is there when the call answers. A LARGER file (a video of several gigabytes) is copied in the background: the call answers at once with status: "importing" and the file_id; call drive.import with the same file again to see bytes_done, and when the copy is over it answers with the finished file (status: "ready"), whose download link files.info gives. Such a file is stored only: it is not searchable. Importing the same file again after it changed in Drive adds a new version of the same file_id; if it has not changed, nothing is downloaded (unchanged: true). A change made in Google Docs by someone else in the last few minutes may not be seen as a change yet; importing again a few minutes later picks it up. file is a Drive id or a pasted link.

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": {
      "file": "<file>"
    },
    "name": "drive_import"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesDrive id or pasted link of the file.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Rich disclosure beyond the annotations: conversion formats (.docx/.xlsx/.pdf, 10 MB cap), the 50 MB synchronous/background threshold, the status/bytes_done/file_id polling contract, and the caveat that a large file is stored but not searchable. It also explains versioning and Docs eventual-consistency delays. Slight misfit with idempotentHint=false is not a contradiction since re-imports can create new versions, and error/permission behavior is unstated.

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?

Front-loaded with purpose, then size/conversion behavior, then the polling loop and versioning. Every sentence carries information, though the parenthetical '(a video of several gigabytes)' and repeated 'call drive.import with the same file again' phrasing add some bulk.

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?

Covers the hard parts of a complex operation — conversion, size thresholds, asynchronous status, versioning, staleness — with no output schema to lean on. The remaining gap is the unexplained premise of 'registered Google Drive folders' and a lack of error or permission guidance, which an agent may need to recover from failures.

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 coverage is 100%, so the baseline is 3; the description adds a small but real clarification for `file` by saying it accepts a pasted link as an alternative to an id, which reinforces the schema rather than merely repeating it. The `in_workspace` override is left entirely to the schema.

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 first sentence states a specific verb and resource — bringing a Drive file into the workspace's files — and names what becomes possible downstream (search, knowledge, files.read), which separates it from siblings like drive_read or drive_search that only inspect Drive content.

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?

It is clear when this tool applies (copy a Drive file into the workspace so other tools can use it) and it gives explicit re-use guidance: re-importing after a change adds a version, unchanged files download nothing, and a large file requires calling again to poll. It never explicitly names drive_read as the read-only alternative, so it stops short of full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.