Skip to main content
Glama

Dropbox

by io.github.pipeworx-io

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesFolder path (e.g., "" for root, "/Documents")
limitNoMax entries to return (default 100)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoError code if connection failed
cursorNoPagination cursor for more results
entriesNoArray of files and folders in the directory
messageNoError message if connection failed
has_moreNoWhether more entries exist

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • 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"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "path": ""
+  },
+  {
+    "limit": 50,
+    "path": "/Documents"
+  }
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the description doesn't need to restate safety. It adds useful behavioral context by noting the return fields (names, types, sizes, modification dates) and the directory-listing concept, though it doesn't disclose pagination or recursion behavior. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loaded with the core function, and contains no redundant or irrelevant information. Every word earns its place.

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?

For a simple listing tool with only two parameters, an output schema, and complete safety annotations, the description covers the essential purpose and use case. It is fully adequate for an agent to select and invoke the tool correctly.

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?

The input schema covers both parameters with 100% description coverage, so the schema handles the semantic burden. The description adds minimal extra meaning beyond confirming the path concept and listing use case, which is already implied by the schema. Baseline 3 is appropriate.

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 clearly states the tool lists files and folders in a Dropbox directory, with a specific verb and resource. It distinguishes itself from sibling tools like dropbox_create_folder and dropbox_download by focusing on listing, and specifies the returned metadata (names, types, sizes, modification dates).

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?

The description explicitly states when to use the tool: 'Use when browsing folder contents or checking what's stored at a path.' It provides clear context for the intended use case, though it does not explicitly mention when to prefer alternatives like dropbox_search or dropbox_get_metadata.

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

All Dropbox toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation2/5

The server name 'Dropbox' leads agents to expect file storage operations, but only 5 of 35 tools are Dropbox-specific. The majority are Pipeworx data lookup and prediction market tools, creating a confusing mismatch between server identity and toolset.

Naming Consistency2/5

Dropbox tools consistently use 'dropbox_verb_noun', but Pipeworx tools mix naming styles: some use 'verb_noun' like 'validate_claim', others use descriptive phrases like 'entity_profile' or 'recent_changes'. The overall set lacks a unified naming convention.

Tool Count2/5

35 tools is high, and the majority are unrelated to the server's name. The Dropbox subset alone is appropriately scoped with 5 tools, but the inclusion of 30 misc data tools makes the set feel bloated and unfocused for a server purportedly dedicated to Dropbox.

Completeness2/5

For the Dropbox domain, the tools cover only basic operations (create folder, download, list, search, metadata) missing update, delete, share. For the Pipeworx domain, the toolset is extensive, but the overall combination lacks completeness for any single coherent purpose.

Resources