Skip to main content
Glama

drive_list_files

Read-onlyIdempotent

Search Google Drive and return matching file metadata—IDs, names, MIME types, owners, sharing status, and links—within a result limit; privacy settings may redact fields.

Instructions

Search Google Drive and return matching file metadata (id, name, mime_type, owners, sharing status). Returns a list of {id, name, mime_type, size, created_time, modified_time, owners, shared, web_view_link, parent_ids, drive_id, thumbnail_link, tags}: at most max_results files (default 20, capped at 1000), read across pages, in the order the Drive API gives for the query; fields may be redacted by the user's privacy settings. Use drive_list_folder to list one folder's children, or drive_get_file_metadata when you already have a file's id. Auto-approved.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>",
      "reason": "<reason>"
    },
    "name": "drive_list_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesDrive API 'q' search query syntax, not a plain-text search string, e.g. "name contains 'Foo'" or "fullText contains 'Foo'". See https://developers.google.com/drive/api/guides/search-files
reasonYesOne sentence: why are you calling this tool right now?
max_resultsNoMost files to return. Default 20, capped at 1000. Reads up to max_results items across pages.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / max_results / description
      Added value: +"Most files to return. Default 20, capped at 1000. Reads up to max_results items across pages."
  2. First observedv5.3.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent and non-destructive, and the description still adds real behavior: results are read across pages up to max_results, capped at 1000, returned in the Drive API's query order, and fields may be redacted by the user's privacy settings. The redaction and ordering disclosures are things an agent cannot infer from the schema or annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and alternatives are front-loaded, but the field list is stated twice: once as "(id, name, mime_type, owners, sharing status)" and again as a full object literal including size, timestamps, links, parent_ids and tags. That duplication costs space without adding information.

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?

With no output schema, the description usefully enumerates the returned shape, and it covers pagination, cap and redaction. Minor gaps remain: opaque fields like tags and drive_id are unexplained, and nothing is said about behavior when the query matches more than the cap or when the query syntax is malformed.

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 coverage is 100%, so query syntax, the reason field and the default/cap behavior are already documented in the schema. The description restates the default 20 / cap 1000 but adds no new semantics for the query 'q' syntax or the reason parameter. Baseline 3 applies when the schema carries the parameter burden.

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?

The description opens with a specific verb and resource ("Search Google Drive and return matching file metadata") and immediately names what the results look like. It distinguishes itself from drive_list_folder and drive_get_file_metadata by stating exactly which scope each of those covers instead.

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

Usage Guidelines5/5

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

It names two concrete alternatives with the condition that selects each: drive_list_folder for one folder's children, drive_get_file_metadata when the file id is already known. It also signals the tool is auto-approved, so an agent knows no extra confirmation path is needed.

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