Skip to main content
Glama
Sign In
Hermoso

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

List Google Drive files

list_drive_files
Read-onlyIdempotent

List Google Drive files and folders Hermoso can reach—created or picked—to find file IDs. Filter by name, folder, or folders only; paginate and list recursively. Read-only.

Instructions

List the Google Drive files & folders Hermoso can reach: the ones it created plus any the user picked with the Google file picker in the app (drive.file, never their whole Drive). This is how you find a picked file's id. Filter by query (name contains …), folderId, or onlyFolders:true; paginate with pageToken. Read-only. A FOLDER: picking a folder hands over the folder alone, not its files, so a folder can list empty or partly; the reply then carries pickUrl, an app link that opens the picker inside that folder (Cmd+A / Ctrl+A selects every file and subfolder). Give the user that exact link, then list again. recursive:true walks every subfolder Hermoso can see (each row has its path) and reports picked files whose folder it cannot see.

Input Schema

NameRequiredDescriptionDefault
queryNoonly files whose name contains this
folderIdNolist the contents of this folder id
pageSizeNorows per page (1–200, default 50)
pageTokenNocursor from a previous call
recursiveNowith folderId: the whole tree
onlyFoldersNolist folders only
includeTrashedNoinclude trashed files (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.435
    • addedInput schema / properties / recursive
      Added value: +{
+  "description": "with folderId: the whole tree",
+  "type": "boolean"
+}
  2. Changed1 schema field changedv0.1.161
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "cursor": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "files": {
-      "items": {},
-      "type": "array"
-    }
-  },
-  "type": "object"
-}New value: +null
  3. Addedv0.1.15

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/non-destructive, yet the description adds substantial non-obvious behavior: the drive.file scope limit, the folder-pick gotcha ('a folder can list empty or partly'), the pickUrl round-trip, the Cmd+A/Ctrl+A trick, and that recursive lists picked files whose folder it cannot see. This is well beyond the annotation surface.

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?

Front-loads what it does before the workflow detail, and the folder-picker paragraph is dense but each clause carries operational weight. It is fairly long and somewhat run-on, which keeps it off a 5.

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 7-param, no-output-schema tool, it explains return content (pickUrl, per-row path) and the edge cases (empty/partial folders, invisible parents) that an agent needs to call it correctly.

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 real meaning on top: recursive 'walks every subfolder Hermoso can see' with a `path` per row, and clarifies query/folderId/onlyFolders/pageToken behavior. pageSize and includeTrashed are left to the schema, so not a full 5.

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?

States a specific verb (List) and resource (Google Drive files & folders) and immediately bounds the scope: 'the ones it created plus any the user picked ... (drive.file, never their whole Drive).' This scope statement alone distinguishes it from list_onedrive_files and from the broader Drive siblings.

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?

Gives clear operating context: 'This is how you find a picked file's id,' when to use folderId/onlyFolders/recursive, and the Cmd+A picker workflow for empty folders. It never names a sibling alternative explicitly (e.g. get_drive_file for reading a known id), so it stops short of the 5 bar.

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