Skip to main content
Glama
HuntsDesk

Google Workspace MCP VE

by HuntsDesk
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

list_drive_items

List files and folders in a Google Drive folder, including shared drives. Supports pagination, filtering by file type, and ordering by various properties.

Instructions

List files in one Drive folder (children of folder_id).

Use this to browse by folder; for content-based search use search_drive_files. Scoped to a folder's direct children. If drive_id is set, folder_id is interpreted inside that shared drive. Requires the drive.readonly OAuth scope.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_google_emailYesThe user's Google email address (authenticated account).
folder_idNoFolder ID to list. "root" = My Drive root. For a shared drive, pass the drive ID to list its root or a folder ID within it. Default "root".root
page_sizeNoMax items returned, 1-1000. Default 100.
page_tokenNoCursor from a prior response's `nextPageToken`.
drive_idNoShared drive ID to scope the listing. Omit for My Drive + shared-with-me.
include_items_from_all_drivesNoTrue (default) to include shared drive items when drive_id is omitted.
corporaNo"user", "drive", or "allDrives". Defaults to "drive" when drive_id is set.
file_typeNoFriendly alias ("folder", "doc", "sheet", "slides", "pdf", etc.) or raw MIME type. Filters to that type only.
detailedNoTrue (default) includes size, modified time, webViewLink; False returns just name/ID/type.
order_byNoComma-separated sort keys with optional " desc", e.g. "folder,modifiedTime desc". Valid keys: createdTime, folder, modifiedByMeTime, modifiedTime, name, name_natural, quotaBytesUsed, recency, sharedWithMeTime, starred, viewedByMeTime.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed10 schema fields changedv1.0.0
    • changedInput schema / properties / corpora / description
      Previous value: -"Corpus to query ('user', 'drive', 'allDrives'). If `drive_id` is set and `corpora` is None, 'drive' is used. If None and no `drive_id`, API defaults apply."New value: +"\"user\", \"drive\", or \"allDrives\". Defaults to \"drive\"\nwhen drive_id is set."
    • changedInput schema / properties / detailed / description
      Previous value: -"Whether to include size, modified time, and link in results. Defaults to True."New value: +"True (default) includes size, modified time,\nwebViewLink; False returns just name/ID/type."
    • changedInput schema / properties / drive_id / description
      Previous value: -"ID of the shared drive. If provided, the listing is scoped to this drive."New value: +"Shared drive ID to scope the listing. Omit for My\nDrive + shared-with-me."
    • changedInput schema / properties / file_type / description
      Previous value: -"Restrict results to a specific file type. Accepts a friendly\n                       name ('folder', 'document'/'doc', 'spreadsheet'/'sheet',\n                       'presentation'/'slides', 'form', 'drawing', 'pdf', 'shortcut',\n                       'script', 'site', 'jam'/'jamboard') or any raw MIME type\n                       string (e.g. 'application/pdf'). Defaults to None (all types)."New value: +"Friendly alias (\"folder\", \"doc\", \"sheet\", \"slides\",\n\"pdf\", etc.) or raw MIME type. Filters to that type only."
    • changedInput schema / properties / folder_id / description
      Previous value: -"The ID of the Google Drive folder. Defaults to 'root'. For a shared drive, this can be the shared drive's ID to list its root, or a folder ID within that shared drive."New value: +"Folder ID to list. \"root\" = My Drive root. For a\nshared drive, pass the drive ID to list its root or a folder\nID within it. Default \"root\"."
    • changedInput schema / properties / include_items_from_all_drives / description
      Previous value: -"Whether items from all accessible shared drives should be included if `drive_id` is not set. Defaults to True."New value: +"True (default) to include shared\ndrive items when drive_id is omitted."
    • changedInput schema / properties / order_by / description
      Previous value: -"Sort order. Comma-separated list of sort keys with optional 'desc' modifier.\n                      Valid keys: 'createdTime', 'folder', 'modifiedByMeTime', 'modifiedTime',\n                      'name', 'name_natural', 'quotaBytesUsed', 'recency', 'sharedWithMeTime',\n                      'starred', 'viewedByMeTime'. Example: 'modifiedTime desc' or 'folder,modifiedTime desc,name'.\n                      Defaults to None (Drive API default ordering)."New value: +"Comma-separated sort keys with optional \" desc\", e.g.\n\"folder,modifiedTime desc\". Valid keys: createdTime, folder,\nmodifiedByMeTime, modifiedTime, name, name_natural,\nquotaBytesUsed, recency, sharedWithMeTime, starred,\nviewedByMeTime."
    • changedInput schema / properties / page_size / description
      Previous value: -"The maximum number of items to return. Defaults to 100."New value: +"Max items returned, 1-1000. Default 100."
    • changedInput schema / properties / page_token / description
      Previous value: -"Page token from a previous response's nextPageToken to retrieve the next page of results."New value: +"Cursor from a prior response's `nextPageToken`."
    • changedInput schema / properties / user_google_email / description
      Previous value: -"The user's Google email address. Required."New value: +"The user's Google email address (authenticated\naccount)."
  2. First observedv1.19.0

TDQS

A4.5/5.0
Behavior4/5

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

Without annotations, the description provides good behavioral context: read-only operation (drive.readonly scope), lists direct children, and shared drive behavior. It could mention pagination implicitly but parameters cover 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?

The description is four concise sentences, front-loaded with core purpose, followed by usage guidance, scope clarification, and authentication. Every sentence adds value.

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?

Given the tool's complexity (10 parameters, 1 required), the description covers use case, alternatives, scope, and authentication. Output schema exists, so return values need not be described.

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 baseline is 3. The description adds high-level context (folder_id as main parameter, drive_id interaction) but mostly repeats schema info.

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 clearly states the verb "List" and the resource "files in one Drive folder (children of folder_id)". It distinguishes from sibling tool "search_drive_files" and specifies the scope (direct children) and shared drive interpretation.

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?

The description explicitly states when to use this tool (browse by folder) and when to use the alternative (search_drive_files for content-based search). It also covers scope and OAuth scope requirement.

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