Skip to main content
Glama

Import from Google Drive

import_from_google_drive

Import Google Drive folders into a board. Use this for files that live in the user's Google Drive, including private folders — upload_from_url cannot reach those. Google Drive and Dropbox are connected ONCE, by a person, in the Playbook web app — there is no tool that connects them. Connections belong to a Playbook user: this server only sees connections made by the same Playbook account it is signed in as. When list_import_sources has no source with the needed provider, its connect_url is where a person connects that service; the source is listed once they have. Every folder is checked against the connected Google account first; one it cannot see is refused with the account's email, which usually means the folder must be shared with that account. RE-SYNC: importing the same folder into the same board_token skips files already there unchanged, so a recurring sync should reuse the board. But a file changed in Drive is added as a SECOND asset next to the old one, and renaming the Drive folder or its sub-board imports that folder again in full. WHERE FILES LAND: each folder becomes a sub-board NAMED AFTER THE FOLDER inside the target board, with its sub-folders nested below — not the target board itself. Find it with list_board_children on board_token, or list_assets with nested_assets. The import is ASYNCHRONOUS: this returns a run in pending; poll get_import until status is completed or canceled. Plans without unrestricted imports allow one active import per workspace; the refusal names the active import's token, so poll that instead of retrying. Storage overage cannot be agreed to here: the call is refused when the workspace has no storage left before overage it has not agreed to, and the import is canceled (overlimit) before storing a file that would cross it. A rate-limit error carries a retry delay — wait that long. Requires a write-scope token and workspace owner/admin permission.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
foldersYes1–20 Google Drive folder URLs (https://drive.google.com/drive/folders/…) or bare folder IDs. Folders only — a file URL is refused.
board_tokenNoBoard to import into; each folder lands in a sub-board of it. Omit to create a new top-level board named 'Google Drive import (date)'; pass the board from an earlier run to re-sync it. A deleted board is not found.
organizationNoWorkspace slug, as returned by list_organizations. Omit it when the account has a single workspace — it is then resolved from your token. Pass it only when the account has several, or when you mean a workspace other than the obvious one.
source_tokenYesToken of a `google_drive` source from list_import_sources

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / context
      Removed value: -{
      -  "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
      -  "type": "string"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "source_token",
      -  "folders",
      -  "context"
      -]New value: +[
      +  "source_token",
      +  "folders"
      +]
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true) only sketch the safety profile; the description adds substantial non-obvious behavior: asynchronous run in `pending`, per-folder validation against the connected account, re-sync dedup but duplicate-on-change and full re-import on rename, storage-overage refusal/cancel, rate-limit retry delay, and write-scope plus owner/admin auth requirements.

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?

Long but front-loaded and organized with ALL-CAPS section markers (RE-SYNC, WHERE FILES LAND) so an agent can scan it. Nearly every sentence carries distinct operational information, though a few clauses (storage overage detail) could be tightened.

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?

No output schema exists, and the description compensates by explaining the return (a run in `pending` with get_import polling to completed/canceled) and failure modes. For a complex, async, externally-dependent import tool, nothing essential is missing.

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 schema carries the field docs (baseline 3). The description adds meaning beyond it, notably the board_token reuse pattern for re-sync and where imported folders land as sub-boards, which an agent needs to pick board_token correctly.

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 ('Import Google Drive folders into a board') and immediately scopes it against the sibling it is not ('upload_from_url cannot reach those' private folders). An agent can distinguish it from upload_from_url and import_from_dropbox without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes: use this for user's Drive files including private folders; connects are done by a person in the web app via list_import_sources connect_url; reuse the board_token for recurring sync. It also names the async follow-up (poll get_import) and the one-active-import constraint with the alternative (poll the named token).

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.

Resources