Skip to main content
Glama
Sign In
Google Workspace MCP Server

Google Workspace MCP Server

by tom275275
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_docs_in_folder

List all Google Docs in a specific Drive folder by providing your Google email and optional folder ID. Returns a formatted list of documents for quick review.

Instructions

Lists Google Docs within a specific Drive folder.

Returns: str: A formatted list of Google Docs in the specified folder.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "user_google_email": "<user_google_email>"
    },
    "name": "list_docs_in_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
folder_idNoroot
page_sizeNo
user_google_emailYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.14.3

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, but it only says the tool 'Lists' and 'Returns a formatted list'. It does not disclose read-only safety, authentication requirements, pagination behavior, or what happens when folder_id is invalid.

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

Conciseness3/5

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

The description is short and front-loaded, but the 'Returns' block adds little value and no parameter or usage detail is included. It is concise but under-specified.

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 tool with three parameters, no annotations, and many closely related siblings, this description omits essential operational context. An agent cannot tell how to properly set folder_id, why user_google_email is required, or how pagination works.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not compensate. folder_id, page_size, and user_google_email are never explained, even though user_google_email is required and page_size defaults to 100.

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 states a clear action and resource: it lists Google Docs within a specific Drive folder. This distinguishes it from many sibling tools, though it does not explicitly contrast with list_drive_items or search_drive_files.

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 guidance on when to use this tool versus alternatives such as list_drive_items or search_drive_files. No context, prerequisites, or exclusions are provided.

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

Deploy Server

Other Tools