Skip to main content
Glama
webapper-services

CloudSee Drive MCP Server

by webapper-services
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Browse folder

browse_folder
Read-only

Browse a drive folder to list its files and subfolders, with sorting and pagination. Keep calling with the returned cursor to get all entries.

Instructions

List the files and sub-folders inside a folder of a drive (the indexed view), with sorting and pagination. Requires the drive (bucketName). To filter by keyword use 'search_files'; for a complete, recursive file listing straight from storage use 'list_files'. For a complete listing, keep calling with the returned cursor until no cursor comes back — a page may be short, or even empty, while more results remain.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoFolder path / prefix within the drive to list. Empty or omitted = the drive root.
cursorNoOpaque pagination cursor returned by a previous call.
pageSizeNoMax items per page (1-200, default 13). The connector sizes each page to what it can render whole, starting at 13 and adapting to the size of your items from the previous page; a larger value is reduced to what fits.
bucketNameNoThe CloudSee drive (S3 bucket) name to operate in, e.g. 'max-2778abc0' — find it in the CloudSee dashboard. Required unless CLOUDSEE_DEFAULT_BUCKET is configured on the server.
sortOptionNoSort key, e.g. 'name_asc', 'name_desc', 'date_desc'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.1.1
    • changedInput schema / properties / pageSize / description
      Previous value: -"Max items per page (1-200, default 50)."New value: +"Max items per page (1-200, default 13). The connector sizes each page to what it can render whole, starting at 13 and adapting to the size of your items from the previous page; a larger value is reduced to what fits."
  2. First observedv1.0.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description is consistent with them. It adds genuine behavioral detail beyond annotations by clarifying that this is the 'indexed view' and that a page may be short or empty while more results remain, which is important for correct pagination.

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?

Three sentences, each earning its place: purpose and features first, sibling routing second, pagination caveat third. No filler or redundant restatement of the schema.

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 read-only listing tool with 100% schema coverage, the description covers purpose, alternatives, a required parameter, and a non-obvious pagination behavior. It doesn't detail the exact return shape, but the tool has no output schema and 'files and sub-folders' gives a sufficient high-level expectation.

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 100%, so the baseline is 3, but the description adds value by emphasizing that bucketName is required and by explaining cursor semantics ('keep calling until no cursor comes back') beyond the schema's one-line cursor definition.

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 opens with a specific verb and resource: 'List the files and sub-folders inside a folder of a drive (the indexed view), with sorting and pagination.' It also names sibling tools search_files and list_files as alternatives, so an agent can clearly distinguish this tool from similar ones.

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?

It states a hard requirement (bucketName), routes keyword filtering to search_files, and recursive storage listing to list_files. It also instructs the agent to keep calling with the returned cursor until none comes back, covering the correct iterative usage pattern.

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

Deploy Server

Other Tools