Skip to main content
Glama
Google Workspace (GWS) MCP Server

Google Workspace (GWS) MCP Server

drive_files_list

Read-only

List and search files in Google Drive with query filters, field selection, sorting, and pagination; shared drive files are included automatically.

Instructions

List files in Google Drive. Supports search queries via the 'q' parameter. Shared drive files are included automatically.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "drive_files_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoSearch query (e.g. "name contains 'report'" or "mimeType='application/vnd.google-apps.folder'")
fieldsNoFields to include (e.g. "files(id,name,mimeType)")
orderByNoSort order (e.g. "modifiedTime desc")
pageSizeNoMax results per page (1-1000, default 100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered, and the description adds a genuine behavioral fact: shared drive files are included automatically, with no opt-in flag. However it says nothing about pagination, result caps, or query escaping, which are the real behavioral risks for a Drive listing call.

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?

Three short sentences, front-loaded with the core purpose and no filler. The middle sentence about 'q' is mildly redundant with a fully documented schema but is not wasteful enough to penalize heavily.

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?

With no output schema, the description should ideally hint at the return shape (file list plus pagination token) and whether results are truncated by pageSize. It covers purpose and one inclusion behavior but leaves an agent guessing about response structure and how to retrieve subsequent pages.

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%, with examples supplied for q, fields, orderBy, and pageSize, so the schema carries the parameter burden. The description only echoes that 'q' is a search query and adds nothing about how q combines with orderBy or pageSize. Baseline 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?

States a specific verb and resource ('List files in Google Drive'), which lets an agent distinguish it from drive_files_get, drive_files_create, and the other mutating siblings. It stops short of explicitly contrasting with the closest read sibling (drive_files_get), but the resource scope is unambiguous.

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?

There is no guidance on when to use this tool versus drive_files_get, nor when to supply a 'q' search versus listing everything. It also gives no instruction about paginating or following a next page, which matters for a list tool with a pageSize parameter.

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