Skip to main content
Glama

drive list files

drive_list_files
Read-onlyIdempotent

List Google Drive files using an optional raw query, ordering, and pagination filters to locate documents, PDFs, or other items without modifying them.

Instructions

List Drive files with an optional raw Drive query (e.g. "mimeType='application/pdf'"). Read-only.

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_list_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
order_byNomodifiedTime desc
page_sizeNo
page_tokenNo
include_trashedNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so 'Read-only.' adds nothing beyond the structured data. No pagination behavior, default ordering, or trashed-item handling is disclosed despite page_token/page_size/order_by/include_trashed existing.

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 front-loaded and short, with the query capability stated before any caveat. The trailing 'Read-only.' sentence is redundant with the annotations, slightly reducing the density of useful content.

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?

An output schema exists, so return values need not be explained, but the tool has five parameters including pagination and a trash flag with zero schema documentation and no description coverage. For a paginated listing tool, missing page_size/page_token/order_by semantics leaves an agent guessing at invocation details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for five parameters, so the description must compensate and largely does not. It explains the query parameter with a concrete syntax example, but order_by, page_size, page_token, and include_trashed are left entirely undocumented in both schema and description.

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 gives a specific verb and resource ('List Drive files') and adds the notable capability of accepting a raw Drive query, which an agent can distinguish from a plain listing. It stops short of differentiating this from the sibling drive_search_files, so an agent cannot tell from the text alone which listing tool to pick.

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 when-to-use or when-not-to-use guidance, and no mention of the obvious alternative drive_search_files, which is a sibling with an overlapping surface. The only usage signal is that the query parameter is 'optional', which does not tell an agent under what conditions to supply one.

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