Skip to main content
Glama

drive_list

Read-onlyIdempotent

List the Google Drive folders registered for this workspace, or the contents of one folder inside them (id, name, type, modified, size, link). Omit folder to get the registered roots. folder is a Drive id or a pasted link. Page with page_token from the previous answer's next_page_token.

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

Input Schema

NameRequiredDescriptionDefault
kindNoOnly with `folder`: folder, doc, sheet or file.
folderNoFolder id or link inside a registered root. Omit to list the roots.
page_tokenNonext_page_token of the previous answer.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already state readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds behavior the annotations do not: which fields come back (id, name, type, modified, size, link) and the pagination contract via next_page_token. It does not discuss permissions, rate limits, or caps on result size.

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 tight sentences with no filler, and the primary behavior (list roots) is front-loaded before the folder variant and pagination. The parenthetical field list is compact and earns its space; wording is dense but readable.

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 compensates by enumerating returned fields, and it covers the root/contents branch and pagination loop. The workspace-override parameter is not mentioned, but the schema documents it fully, so nothing needed to call the tool correctly is missing.

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%, so the baseline is 3. The description reinforces `folder` as a Drive id or pasted link and ties `page_token` to next_page_token, which slightly sharpens the schema wording, but `kind` and `in_workspace` are left entirely to the schema.

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 opens with a specific verb and resource: it lists registered Google Drive folders for the workspace, or the contents of one folder. The root-vs-contents scope is explicit. It does not name a sibling such as drive_search or drive_read, so the agent learns the boundary from the resource noun rather than from an explicit contrast.

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

Usage Guidelines4/5

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

It gives clear selection rules for its own modes: omit `folder` to get the registered roots, supply one to list inside it, and page with the previous answer's next_page_token. It stops short of saying when to prefer this over drive_search or drive_read, so the alternative-tool guidance is absent.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.