Skip to main content
Glama
EveryInc

google-workspace-mcp-server

by EveryInc

Search Drive Files

drive_search_files
Read-onlyIdempotent

Search Google Drive files by name or content. Filter by type (documents, spreadsheets, presentations, folders) and paginate results.

Instructions

Search for files in your Google Drive by name or content.

Args:

  • query (string): Search query - searches file names and content

  • page_size (number): Max files to return, 1-100 (default: 20)

  • page_token (string, optional): Pagination token for next page

  • mime_type ('all' | 'documents' | 'spreadsheets' | 'presentations' | 'folders'): Filter by type (default: 'all')

  • response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: For JSON format: { "files": [ { "id": string, "name": string, "mimeType": string, "createdTime": string, "modifiedTime": string, "size": string, "webViewLink": string, "owners": string[] } ], "next_page_token": string | null }

Examples:

  • Search by name: query="budget 2024"

  • Search spreadsheets: query="sales", mime_type="spreadsheets"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query - searches file names and content
page_sizeNoMaximum number of files to return (1-100)
page_tokenNoToken for pagination to retrieve the next page of results
mime_typeNoFilter by file typeall
response_formatNoOutput format: 'markdown' for human-readable or 'json' for structured datamarkdown
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, covering the safety profile. The description adds pagination, filtering, and output format details, which are useful but not critical beyond annotations.

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 well-structured with clear sections (Args, Returns, Examples). It is concise yet complete, front-loading the purpose and providing necessary details without verbosity.

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 5 parameters, full schema, rich annotations, and no output schema, the description compensates with return format and examples, making it fully complete for an agent to invoke correctly.

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 repeats parameter info but adds examples and return format, which clarifies usage but does not significantly extend schema semantics.

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 it searches files by name or content in Google Drive, differentiating from sibling tools like drive_list_files (list without query) or drive_get_file (get specific file by ID).

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?

The description implies usage for searching, but does not explicitly state when to use vs. alternatives (e.g., drive_list_files for unfiltered listing). However, the query parameter and examples guide appropriate usage.

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/EveryInc/google-workspace-mcp-server'

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