Skip to main content
Glama

dropbox_import_file

Import an original file from the user's connected Dropbox into this project's media library. Use it only when the task needs the media itself (editing, transcription, frames). Pass fileId and expectedRevision from dropbox_list_files or from a file the user attached. Returns assetId; use it like any other media. Importing the same revision again reuses the asset.

Errors: a revision mismatch means the file changed after it was listed; list it again and confirm with the user before using the new version. Keep the project's editor tab open. Not connected or expired: manage_connectors action=connect.

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>"
    },
    "name": "dropbox_import_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileIdYesFile ID from the listing or an attached file.
projectIdNoProject for this call (full ID or unambiguous prefix). Explicit-timeline calls never change the target of later calls; legacy project selection applies otherwise.
timelineIdNo
accountTargetNoExact account {accountId, revision} from list_connectors. Required on every platform call.
expectedRevisionNoThe file revision from that same listing or attachment; the import stops if the file changed.
skipTranscriptionNotrue when the task does not need speech, such as B-roll or images. Omit it when you will edit by speech or make captions.

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?

Annotations already declare this is a non-read, non-destructive operation, and the description adds meaningful context on top: the deduplication behavior ('Importing the same revision again reuses the asset'), the optimistic-concurrency guard on expectedRevision, a named failure mode with remediation, and the precondition 'Keep the project's editor tab open.' That open-tab requirement is real operational guidance not present in any structured field. Minor tension: 'reuses the asset' reads as effectively idempotent while idempotentHint is false, and the text does not say whether a re-import re-triggers transcription.

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?

The text is short and front-loaded: identification and the call precondition come first, then the return value, then a compact 'Errors' block that pairs each failure with a remediation. A few phrasings are slightly redundant ('use it like any other media' restates 'into this project's media library'), but nothing wastes a full sentence.

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 6-parameter mutating tool with no output schema and a nested accountTarget object, the description covers the essential gaps: the precondition on the listing, the return identifier, the revision-conflict recovery, and the connect-and-retry path. The accountTarget and project/timeline scoping are left entirely to their schema descriptions, which is acceptable given their coverage but means the description never explains the account-target requirement in prose.

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 83%, so the baseline would be 3, but the description earns more by telling the agent where the two key values originate ('Pass fileId and expectedRevision from dropbox_list_files or from a file the user attached') and by spelling out the consequence of a revision mismatch, which the schema only states tersely. It also frames the return in terms of what the agent does next ('Returns assetId; use it like any other media'), linking the output to downstream tools.

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 description names a specific verb and resource with its source and destination: 'Import an original file from the user's connected Dropbox into this project's media library.' It also implicitly separates itself from the listing sibling by telling the agent to pass fileId from dropbox_list_files, so an agent does not confuse gathering metadata with importing the media itself.

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 gives an explicit inclusion condition ('Use it only when the task needs the media itself (editing, transcription, frames)'), which effectively excludes metadata-only work. It also routes the agent to dropbox_list_files for the required values and gives a recovery path for expired connections. It stops short of contrasting with the generic import_media sibling, leaving the agent to infer which import path applies to a local file.

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.