Skip to main content
Glama
EveryInc

google-workspace-mcp-server

by EveryInc

List Drive Files

drive_list_files
Read-onlyIdempotent

List files from your Google Drive with filters by type, sort order, and pagination to retrieve results in markdown or JSON format.

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
page_sizeNoMaximum number of files to return (1-100)
page_tokenNoToken for pagination to retrieve the next page of results
order_byNoSort order (e.g., 'modifiedTime desc', 'name', 'createdTime desc')modifiedTime desc
mime_typeNoFilter by file typeall
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 and idempotentHint; description adds valuable details about pagination (next_page_token) and response structure, which go beyond annotations. No contradictions.

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?

Well-structured with clear 'Args' and 'Returns' sections, bullet points, and front-loaded purpose. Slightly verbose with repeated default values, but overall efficient and scannable.

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?

Despite lack of output schema, the description explicitly documents the JSON return format, including fields and pagination. Handles all aspects: filtering, ordering, pagination, and output format. No missing context for a filtered-list tool.

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?

All parameters already described in schema (100% coverage). The description adds useful context by showing default values, sort order examples, and the return format structure, which exceeds the schema's minimal descriptions.

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?

Clearly states 'List files in your Google Drive' with specific verb and resource. However, it does not distinguish from sibling 'drive_search_files' which also lists files but likely with more advanced search capabilities.

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?

No explicit guidance on when to use this tool versus alternatives like 'drive_search_files'. The parameter descriptions imply usage for filtering by type and ordering, but no contextual direction is provided.

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

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