Skip to main content
Glama

Playbook

by com.playbook
OverviewDiscussionsAdmin

Import from Dropbox

import_from_dropbox

Import Dropbox folders into a board. Use this for files that live in the user's Dropbox, including private and team 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. FOLDERS: pass the folder URL from the Dropbox address bar (https://www.dropbox.com/home/… on a personal account, /work/… for a team member), its path (/Clients/Acme), or an id: key. Shared links (dropbox.com/scl/…) are refused; the address-bar URL or the path is required. Every folder is checked against the connected Dropbox account first; one it cannot find is refused with the account's email. RE-SYNC: importing the same folder into the same board_token skips files already there unchanged (compared by Dropbox content hash), so a recurring sync should reuse the board. A file changed in Dropbox is added as a SECOND asset next to the old one, and renaming the Dropbox folder or its sub-board imports that folder again in full. Files that were first imported before this skipping shipped are downloaded again on every re-sync; the copies are usually merged away, but a workspace with duplicate merging turned off, or an asset kept in a group, ends up with real duplicates. Import into a new board to get skipping for them. 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 Dropbox folders: address-bar URLs (https://www.dropbox.com/home/… or /work/…), paths (/Clients/Acme) or `id:` keys. Folders only — a file, a shared link or the Dropbox root 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 'Dropbox 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 `dropbox` 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.6/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses async execution (returns pending, poll get_import until completed/canceled), the re-sync skip logic and the duplicate-asset risk for changed/renamed folders, one-active-import-per-workspace limits, storage-overage refusal, rate-limit retry delay, and the required write-scope + owner/admin auth. The idempotentHint=false annotation is consistent with the described partial-skip-but-adds-second-asset behavior.

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 structured under clear FOLDERS / RE-SYNC / WHERE FILES LAND headings that make it scannable. It is verbose (~450 words) but the density is warranted by the tool's async, re-sync and duplicate-handling complexity; little is pure filler.

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 fills that gap by explaining what the call returns (a run in pending, polled via get_import) and where imported files land (a named sub-board found via list_board_children or list_assets). Auth, failure modes, and connection prerequisites are all covered.

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 description coverage is 100%, so all four parameters are already documented in the schema, including folder URL/path/id formats, the refused shared-link/root cases, board_token re-sync semantics, and organization resolution. The description largely reinforces rather than extends these, so the baseline 3 applies.

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+resource ('Import Dropbox folders into a board') and immediately distinguishes itself from the closest sibling: 'upload_from_url cannot reach those' for private/team Dropbox folders. An agent can route between this, import_from_google_drive, and upload_from_url without opening any 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?

Explicit when-to-use with the alternative named ('files that live in the user's Dropbox... upload_from_url cannot reach those'), plus guidance for the no-source case ('when list_import_sources has no source... its connect_url is where a person connects'). Re-sync guidance tells the agent when to reuse board_token vs create a new board.

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

All Playbook toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources