Skip to main content
Glama

drive_search

Read-onlyIdempotent

Search and list Google Drive files in a connected account using file-name text, advanced query strings, pagination, and configurable result limits.

Instructions

Search or list Google Drive files in the connected account.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "drive_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoAdvanced Drive query string
limitNoFiles to return (max 100, default 20)
queryNoFile-name search text
page_tokenNoDrive page token from a previous response
access_tokenNoGoogle Drive access token

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered by structured data. The description adds only the 'connected account' scoping note; it says nothing about result caps, pagination flow, or how the query is interpreted.

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

Conciseness4/5

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

One clean sentence with zero padding, appropriately front-loaded. It is efficient rather than verbose, though it leans toward under-specification.

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 5-parameter search/list tool, the description omits how to combine q and query, how page_token chains with limit, and how this differs from drive_read. Annotations and schema cover safety and field meaning, but the operational gaps leave an agent guessing on the core search call.

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 description coverage is 100%, so the baseline is 3. The description contributes nothing about the parameters, and notably does not resolve the ambiguity between 'q' (advanced Drive query string) and 'query' (file-name search text), which is the single most error-prone choice here.

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?

States a specific verb and resource: 'Search or list Google Drive files in the connected account.' An agent knows it queries Drive file listings rather than file contents. It does not distinguish itself from the nearby sibling drive_read, so it stops short of a 5.

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 search versus list, when to use this rather than drive_read, or how to choose between the two search parameters. The agent must infer everything from the parameter names alone.

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