Skip to main content
Glama
nityeshaga

google-workspace-mcp-server

by nityeshaga

List Drive Files

drive_list_files
Read-onlyIdempotent

List files in Google Drive with options for pagination, sorting, type filtering, and output format. View file details like name, ID, and timestamps.

Instructions

List files in your Google Drive.

Args:

  • page_size (number): Max files to return, 1-100 (default: 20)

  • page_token (string, optional): Pagination token for next page

  • order_by (string): Sort order (default: 'modifiedTime desc')

  • mime_type ('all' | 'documents' | 'spreadsheets' | 'presentations' | 'folders'): Filter by type (default: 'all')

  • response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: For JSON format: { "files": [ { "id": string, "name": string, "mimeType": string, "createdTime": string, "modifiedTime": string, "size": string, "webViewLink": string, "owners": string[] } ], "next_page_token": string | null }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
order_byNoSort order (e.g., 'modifiedTime desc', 'name', 'createdTime desc')modifiedTime desc
mime_typeNoFilter by file typeall
page_sizeNoMaximum number of files to return (1-100)
page_tokenNoToken for pagination to retrieve the next page of results
response_formatNoOutput format: 'markdown' for human-readable or 'json' for structured datamarkdown
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, so the safety profile is covered. The description adds behavioral context by explaining pagination (page_token and next_page_token), default sort order, and output format options, which goes beyond the annotations.

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 well-structured with an Args section and a Returns section, using concise bullets and a JSON example. Every part earns its place: parameters, defaults, and return format are all clearly laid out without unnecessary elaboration.

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?

Given that there is no output schema, the description provides a complete return structure including files fields and next_page_token. All five parameters are described with defaults and allowed values. It lacks explicit error-condition handling or rate-limit notes, but for a list tool with rich annotations, it is sufficiently complete.

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 description coverage is 100%, and the description largely restates the schema parameters (page_size, page_token, order_by, mime_type, response_format) with their defaults and enums. It adds minimal new semantic meaning beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 'List files in your Google Drive' with a specific verb and resource. It does not explicitly differentiate from sibling tools like drive_search_files, but the name and basic purpose are clear.

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 is provided regarding when to use this tool versus alternatives. There is no mention of drive_search_files for query-based searching or drive_get_file for retrieving a single file by ID. The description only lists parameters and returns.

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/nityeshaga/google-workspace-mcp-server'

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