Skip to main content
Glama

list_docs_in_folder

List all Google Docs directly inside a given Drive folder. Use it to enumerate docs in a known folder without recursive subfolder search.

Instructions

List all Google Docs (native application/vnd.google-apps.document) that live directly inside a given Drive folder.

Use this when you want to enumerate Docs inside a known folder (e.g., a team drive subfolder). For name-based search across the whole Drive, use search_docs. For non-Doc files (Sheets, Slides, PDFs, etc.) in the folder, use list_drive_items or search_drive_files.

Only direct children are returned — subfolders are NOT recursed. Shared drives are supported via supportsAllDrives=True + includeItemsFromAllDrives=True. Trashed docs are excluded.

Requires OAuth scope: https://www.googleapis.com/auth/drive.readonly (or broader drive scope).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_google_emailYesThe user's Google email address. Required.
folder_idNoDrive folder ID (the string after `/folders/` in the folder URL). Defaults to `"root"` which is the user's My Drive root. For shared drives, pass the shared-drive ID. Passing an invalid or inaccessible folder ID returns "No Google Docs found" (Drive treats missing folders as an empty set rather than raising an error in most cases).root
page_sizeNoMaximum number of docs to return. Defaults to 100. Google's hard cap is 1000. No pagination token is exposed — raise this value if a folder may contain more docs.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Describes non-obvious behaviors: only direct children returned, trashed excluded, shared drive flags needed, and error handling for invalid folders. No annotations were provided, so description carries full burden and meets it.

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?

Concise, front-loaded with purpose, then usage, behavior, auth. Every sentence adds value without repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers scope, alternatives, recursion, shared drives, trashed items, auth scope, and error behavior. Output schema exists so return details not needed. Complete for this tool's complexity.

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%, and schema already has detailed descriptions for each parameter (e.g., folder_id explains default, shared drives, error). Description does not add further parameter details, but baseline 3 is appropriate.

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?

Clearly states 'list all Google Docs directly inside a given Drive folder', specifying verb, resource type, and scope. Distinguishes from siblings like search_docs and list_drive_items by stating when to use each.

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?

Explicitly tells when to use (enumerate Docs in known folder) and when not to, naming alternatives (search_docs for name search, list_drive_items for non-Docs). Also explains no recursion and shared drive support.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/HuntsDesk/ve-gws'

If you have feedback or need assistance with the MCP directory API, please join our Discord server