Skip to main content
Glama

Coline

List files

list_drive_files
Read-onlyIdempotent

Lists files and folders in a drive or folder, or the person's recent or starred files. Follow nextCursor for more.

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": {
      "workspace": "<workspace>"
    },
    "name": "list_drive_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNorecent and starred span every drive; picker lists what can be picked to attach.default
limitNo
cursorNo
driveIdNoDefault: the person's default drive.
trashedNoWhat's in the trash instead.
fileTypeNoOnly folders.
parentIdNoA folder; default: the drive's top level.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
filesYes
driveIdYes
folderIdYes
driveNameYes
nextCursorYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds one genuinely behavioral detail beyond that: the cursor-following pagination contract. It says nothing about trashed mode switching the result set, folder-only filtering, or default ordering, all of which change what an agent sees.

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?

Two short sentences, front-loaded with the resource and its modes, with the pagination note at the end where it belongs. No filler. It could arguably compress the view enumeration since the schema already lists it, but the redundancy is mild.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-value explanation is unnecessary, and the read-only annotations carry the safety burden. Still, for an 8-parameter listing tool with trash, folder-only, and picker modes, the description never signals that these alternate modes exist, leaving the agent to discover them only by reading the schema.

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 75%, so the schema already documents view modes, driveId default, parentId default, and trashed. The description's only real semantic addition is that the cursor parameter should be followed to fetch more pages, which the schema does not explain. Marginal value over structured fields.

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?

The description uses a specific verb ("Lists") with the exact resource ("files and folders") and enumerates the three scoping modes: a drive/folder, recent, or starred. An agent immediately knows what comes back. It stops short of naming a sibling such as list_drives, so the boundary between listing drives versus listing files inside a drive is left implicit.

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?

"Follow nextCursor for more" gives concrete pagination guidance, which is the main usage decision for this tool. However, there is no guidance on when to prefer this over sibling listing tools, nor any statement about prerequisites such as needing a workspace slug before calling. Usage is implied rather than prescribed.

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.

Resources