Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

drive_list_folder

Read-only

Lists files and subfolders in a Google Drive folder, using 'root' for My Drive and pagination to browse large directories.

Instructions

List the contents of a Drive folder ('root' = My Drive).

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

Input Schema

NameRequiredDescriptionDefault
folderIdNoroot
pageSizeNo
pageTokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered without help from the description. Beyond defining 'root', the description adds no behavioral context such as pagination limits, how many results come back, whether the listing is recursive, or what the return shape looks like.

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

Conciseness5/5

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

A single front-loaded sentence with zero padding, and the key clarification about 'root' is placed immediately after the core purpose.

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?

For a listing tool that has three undocumented parameters, no output schema, and open-world pagination behavior, the definition is too thin. An agent has to guess at page size limits and how to page through results in a large folder.

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%, so the description must carry parameter meaning, and it only explains the default value of folderId ('root' = My Drive). Both pageSize (with its 100/200 bounds) and pageToken for paging through large folders go entirely unexplained in the description even though they are important for large folders.

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 the contents of a Drive folder.' It also disambiguates the default value by defining 'root' as My Drive, which lets an agent distinguish it from siblings like drive_search or drive_get_file.

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?

Usage is only implied: an agent can infer that this is the tool for browsing a folder's contents. The description never says when to prefer this over drive_search or drive_get_file, nor does it mention any prerequisites or exclusions.

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