Skip to main content
Glama

google-drive_list_files

List files in Google Drive using search queries, filters, and pagination. Retrieve file details like name, type, size, and modification time.

Instructions

List files in Google Drive with optional search query and filtering

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoSearch query using Drive query syntax (e.g., 'name contains "test"', 'mimeType="application/pdf"', 'parents in "folderId"')
fieldsNoFields to return - IMPORTANT: Must use format 'files(id,name,mimeType,size,modifiedTime,parents,webViewLink)' for list endpoints. Do NOT use 'id,name,mimeType' format.
spacesNoComma-separated list of spaces to query: 'drive', 'appDataFolder', 'photos'
corporaNoCorpora to search: 'user' (default), 'domain', 'drive', 'allDrives'
driveIdNoID of the shared drive to search (if corpora is 'drive')
orderByNoSort order: 'createdTime', 'folder', 'modifiedByMeTime', 'modifiedTime', 'name', 'quotaBytesUsed', 'recency', 'sharedWithMeTime', 'starred', 'viewedByMeTime'
pageSizeNoMaximum number of files to return (default 100, max 1000)
pageTokenNoPage token for pagination
includeLabelsNoComma-separated list of label IDs to include
supportsAllDrivesNoWhether to support files in shared drives
includeItemsFromAllDrivesNoWhether to include files from all drives
includePermissionsForViewNoSpecifies which additional view's permissions to include ('published')
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as pagination, default behavior, or limitations beyond the basic function.

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?

The description is a single, clear sentence. It is concise but could include additional useful information without being verbose.

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

Completeness2/5

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

Given the tool has 12 parameters and no output schema, the description is insufficient. It does not explain pagination, output format, or differentiate from similar tools.

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 has 100% description coverage, so each parameter is explained in the schema. The tool description adds no additional parameter semantics beyond what the schema already provides.

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 clearly states it lists files with optional search and filtering. However, it does not differentiate from the sibling 'google-drive_search_files', which likely has a similar purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives like 'google-drive_search_files'. No mention of context or prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/w-10-m/gsuite'

If you have feedback or need assistance with the MCP directory API, please join our Discord server