Google-Drive-MCP-Server

Overview Schema Source Related Servers Discussions Admin

gdrive_search

Search Google Drive for files by query, filter to a specific shared drive, and paginate results with page size and token.

Instructions

Search for files in Google Drive

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": {
      "query": "<query>"
    },
    "name": "gdrive_search"
  }
}

Input Schema

Name	Required	Description
`query`	Yes	Search query
`driveId`	No	ID of a specific shared drive to search in
`pageSize`	No	Number of results per page (max 100)
`pageToken`	No	Token for the next page of results

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.2Aug 10, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits, but it only states 'search' without explaining whether it is read-only, what scope it covers, or how results are returned. It does not mention pagination, authentication, or limitations, so the agent lacks critical context.

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 a single sentence with no superfluous words. It is front-loaded and immediately communicates the core action, earning full marks for conciseness and structure.

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?

Despite having an input schema with good parameter detail, the tool lacks an output schema and annotations. The description does not clarify return values, query syntax, or potential edge cases, making it incomplete for an agent to use correctly without external knowledge.

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?

The input schema already covers all parameters with descriptions (100% coverage), so the baseline is 3. The description adds no additional meaning beyond what the schema provides, which is acceptable given the high schema coverage.

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 'Search for files in Google Drive' clearly states the verb (search) and the resource (files in Google Drive), distinguishing it from sibling tools like gdrive_read_file and gsheets_read. It is specific and unambiguous.

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?

The description provides no guidance on when to use this tool versus alternatives, such as gdrive_folder_structure or gdrive_read_large_file. It does not mention exclusions or preferred contexts, leaving the agent to infer usage from the tool name alone.

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

Deploy Server