Skip to main content
Glama
Sign In

Dropbox

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Dropbox Search

dropbox_search
Read-onlyIdempotent

Search Dropbox for files and folders by name or content. Returns matching paths, file types, and metadata. Use when you need to find a file without knowing its exact location.

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": {
      "query": "invoice"
    },
    "name": "dropbox_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch query string
max_resultsNoMaximum results to return (default 20)

Output Schema

NameRequiredDescriptionDefault
errorNoError code if connection failed
cursorNoPagination cursor
matchesNoArray of matching files and folders
messageNoError message if connection failed
has_moreNoWhether more results exist

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "cursor": {
+      "description": "Pagination cursor",
+      "type": "string"
+    },
+    "error": {
+      "description": "Error code if connection failed",
+      "type": "string"
+    },
+    "has_more": {
+      "description": "Whether more results exist",
+      "type": "boolean"
+    },
+    "matches": {
+      "description": "Array of matching files and folders",
+      "items": {
+        "properties": {
+          "match_type": {
+            "description": "Type of match (e.g., filename)",
+            "type": "string"
+          },
+          "metadata": {
+            "properties": {
+              "id": {
+                "description": "Unique ID",
+                "type": "string"
+              },
+              "modified": {
+                "description": "Last modified timestamp",
+                "type": "string"
+              },
+              "name": {
+                "description": "File or folder name",
+                "type": "string"
+              },
+              "path_display": {
+                "description": "Display path",
+                "type": "string"
+              },
+              "size": {
+                "description": "File size in bytes",
+                "type": "number"
+              }
+            },
+            "type": "object"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "message": {
+      "description": "Error message if connection failed",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "invoice"
+  },
+  {
+    "max_results": 10,
+    "query": "Q4 report"
+  }
+]
  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=true, idempotentHint=true, and destructiveHint=false. The description adds behavioral context about return values ('matching paths, file types, and metadata') and search capabilities ('by name or content'). It does not mention pagination or rate limits, but the annotation coverage lowers the burden.

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 three concise sentences with no filler. Each sentence earns its place: the first states the action, the second summarizes return data, and the third gives a usage context. It is front-loaded and easy to scan.

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?

This is a simple 2-parameter search tool with an output schema (noted in context signals), so the description does not need to explain return values in depth. Annotations cover safety, and the description provides clear usage context. The tool is well-specified for an agent to select and invoke 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?

Schema coverage is 100% for both parameters (query and max_results). The description adds the semantic nuance that the query searches 'by name or content', but this is already somewhat inferable from the schema and does not add significant new meaning beyond the parameter descriptions.

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 verb ('Search'), resource ('Dropbox'), and scope ('files and folders by name or content'). It distinguishes the tool from sibling Dropbox tools such as dropbox_create_folder, dropbox_download, and dropbox_list_folder by focusing on search functionality.

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 tells when to use the tool ('when you need to find a file without knowing its exact location'). It does not name alternatives directly, but the context is clear enough to differentiate from other Dropbox operations. Lacks explicit exclusions or comparison to search_within, so not a 5.

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
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