Skip to main content
Glama

search

Search across Google Drive and Gmail, then deposit results to a local JSON file for easy access and review.

Instructions

Search across Drive and Gmail.

Writes results to mise/ and returns path + summary.
Read the deposited JSON file for full results.

Args:
    query: Search terms. Optional when type or folder_id is set.
    sources: ['drive', 'gmail'] — default: both (drive only in guest mode). Also: 'activity' (recent comments), 'calendar' (recent events with attachments)
    max_results: Maximum results per source
    base_path: Directory for deposits (pass your cwd so files land next to your project, not the MCP server's directory)
    folder_id: Optional Drive folder ID to scope results to immediate children only.
        Non-recursive — only files directly inside this folder are returned.
        When set, forces sources=['drive'] (Gmail has no folder concept).
    type: Optional Drive file type filter. Applies to Drive only.
        Values: folder, doc, spreadsheet, sheet, slides, presentation, pdf, image, video, form

Returns:
    path: Path to deposited search results JSON
    query: The search query
    sources: Sources searched
    drive_count: Number of Drive results
    gmail_count: Number of Gmail results
    activity_count: Number of Activity results
    calendar_count: Number of Calendar results
    cues: Scope notes and warnings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNo
queryNo
sourcesNo
base_pathNo
folder_idNo
max_resultsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Even without annotations, the description explains writing to files, returning path+summary, and non-recursive behavior. Could more explicitly mention that it creates files.

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?

Well-structured with sections for args and returns, but somewhat lengthy. However, all sentences add value for a complex tool.

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?

Covers all 6 parameters, return fields, edge cases (guest mode, non-recursive), and includes scope notes. Very complete given the tool's complexity and presence of output schema.

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

Parameters5/5

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

With 0% schema coverage, the description fully compensates by explaining each parameter's purpose, defaults, and interactions (e.g., folder_id forces sources=['drive']).

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 across Drive and Gmail, writes results to a file, and returns a path and summary. It distinguishes from siblings ('do', 'fetch') by being a search tool.

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?

Provides detailed when-to-use guidance for each parameter, including when query is optional, default sources, non-recursive folder_id behavior, and scope notes in 'cues'.

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/spm1001/mise-en-space'

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