Skip to main content
Glama
Sign In
MCP Google Multi-Account Server

MCP Google Multi-Account Server

by bkbaheti
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

drive_list_shared_drives

List Google Shared Drives a user belongs to and retrieve drive IDs for browsing or searching files within those drives.

Instructions

List the Shared Drives (Team Drives) the user is a member of. Use the returned drive IDs as the folderId argument to drive_list_files to browse a Shared Drive, or as driveId on drive_search_files to scope a search.

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": {
      "accountId": "<accountId>"
    },
    "name": "drive_list_shared_drives"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageSizeNoMaximum number of drives to return (default: 50, max: 100)
accountIdYesThe Google account ID, alias, or email
pageTokenNoToken for pagination

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.3

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It adds membership scoping ('the user is a member of') and the relationship to other tools, but does not explicitly state read-only semantics, pagination behavior, or potential errors. Since 'List' clearly implies a read operation, the transparency is adequate but not enriched.

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 two sentences, front-loaded with the primary action and immediately followed by the practical use of the results. No redundant information, every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple and there is no output schema, but the description gives enough information for an agent to understand the result type (drive IDs) and how to chain it. It does not describe the full response structure, but the core purpose and downstream usage are covered, making it nearly complete.

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 schema fully documents parameters. The description adds no new parameter details, but it does explain how the output (drive IDs) maps to parameters of other tools, which is helpful context. Baseline 3 is appropriate.

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 the tool lists Shared Drives the user is a member of, using a specific verb and resource. It differentiates from sibling tools by focusing on the drive listing and explicitly referencing how the results feed into drive_list_files and drive_search_files.

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?

The description provides explicit, actionable usage guidance: use the returned drive IDs as folderId for drive_list_files or as driveId for drive_search_files. This tells the agent exactly when and how to use the tool's output, and implies the tool is the entry point for browsing/scoping shared drives.

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