Dropbox

Dropbox List Folder

dropbox_list_folder

Read-onlyIdempotent

List files and folders in a Dropbox directory. Returns names, types, sizes, and modification dates. Use when browsing folder contents or checking what's stored at a path.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": ""
    },
    "name": "dropbox_list_folder"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes	Folder path — "" for the account root, otherwise e.g. "/Documents"
`limit`	No	Max entries to return (default 100)

Output Schema

Name	Required	Description
`error`	No	Error code if connection failed
`cursor`	No	Pagination cursor for more results
`entries`	No	Array of files and folders in the directory
`message`	No	Error message if connection failed
`has_more`	No	Whether more entries exist

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 16, 2026

changedInput schema / properties / path / description

Previous value: -"Folder path (e.g., \"\" for root, \"/Documents\")"New value: +"Folder path — \"\" for the account root, otherwise e.g. \"/Documents\""

addedInput schema / properties / path / minLength
```
Added value: +0
```

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "cursor": {
+      "description": "Pagination cursor for more results",
+      "type": "string"
+    },
+    "entries": {
+      "description": "Array of files and folders in the directory",
+      "items": {
+        "properties": {
+          "id": {
+            "description": "Unique ID for entry",
+            "type": "string"
+          },
+          "modified": {
+            "description": "Last modified timestamp",
+            "type": "string"
+          },
+          "name": {
+            "description": "File or folder name",
+            "type": "string"
+          },
+          "path_display": {
+            "description": "Display path of entry",
+            "type": "string"
+          },
+          "rev": {
+            "description": "Revision identifier",
+            "type": "string"
+          },
+          "size": {
+            "description": "File size in bytes",
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "error": {
+      "description": "Error code if connection failed",
+      "type": "string"
+    },
+    "has_more": {
+      "description": "Whether more entries exist",
+      "type": "boolean"
+    },
+    "message": {
+      "description": "Error message if connection failed",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "path": ""
+  },
+  {
+    "limit": 50,
+    "path": "/Documents"
+  }
+]

First observedApr 22, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered. The description adds useful context about the returned fields, but with an output schema present that is largely redundant, and it says nothing about pagination or how limit interacts with large folders.

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?

Three short sentences with the core operation front-loaded and no filler. It could be tightened slightly by folding the return-field list into the purpose sentence, but nothing is wasted.

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?

With rich annotations, a full output schema, and 100% schema parameter coverage, the remaining burden on the description is light and it meets it: what the tool does and when to reach for it are both covered. Only sibling routing and pagination behavior are missing.

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% and both parameters (path with root-folder convention, limit with default) are documented in-schema. The description adds no syntax or format meaning beyond what the schema already provides, so the baseline 3 applies.

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 and resource (list files/folders in a Dropbox directory) that is unambiguous. However, it never distinguishes itself from close siblings like dropbox_search or dropbox_get_metadata, which an agent browsing the tool list would need help choosing between.

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

Usage Guidelines3/5

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

"Use when browsing folder contents or checking what's stored at a path" gives implied usage, which is adequate context. It stops short of naming alternatives (e.g., dropbox_search for name-based lookup) or stating when not to use this tool.

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

All Dropbox tools Inspect

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.