Skip to main content
Glama
navig-run

NAVIG

Official
by navig-run
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Search Google Drive

connector_google_drive_search
Read-onlyIdempotent

Search Google Drive resources by natural-language query and return matching items, read-only. Use each item's id to fetch full content.

Instructions

Find Google Drive resources matching a query. Read-only: nothing is changed. Returns matching items with their native id, title, preview, url and timestamp; an empty list means nothing matched. Pass an item's id to connector_google_drive_fetch to read it in full.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return (1-50)
queryYesNatural-language query, e.g. 'invoices from Acme last month'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.2
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of results to return"New value: +"Maximum number of results to return (1-50)"
    • addedInput schema / properties / limit / maximum
      Added value: +50
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / query / description
      Previous value: -"Natural-language search query"New value: +"Natural-language query, e.g. 'invoices from Acme last month'"
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so 'Read-only: nothing is changed' largely restates them. However, it adds real value beyond the structured fields by describing the return shape (id, title, preview, url, timestamp) and the empty-list semantics, which matters because there is no output schema.

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?

Four tight sentences, front-loaded with the core purpose and the read-only guarantee, then return shape, then the chaining instruction. No filler.

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?

For a simple 2-parameter search with no output schema, the description covers purpose, safety, return contents, empty-result meaning, and the follow-up tool. Nothing needed to invoke it correctly is missing.

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 both parameters (query, limit) are already documented in the schema, including the 1-50 range and default. The description adds nothing about query syntax beyond the schema's natural-language example, so baseline 3 applies.

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?

States a specific verb ('Find') and resource ('Google Drive resources matching a query'), and explicitly names the sibling connector_google_drive_fetch as the follow-up reader. An agent can distinguish it from fetch without opening either schema.

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?

Gives a clear handoff rule: pass a result's id to connector_google_drive_fetch to read it in full, which tells the agent when to chain the two tools. It does not state explicit exclusions or when-not-to-use, but the retrieval-vs-read split is unambiguous.

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