Skip to main content
Glama

drive_folders

Read-onlyIdempotent

Manage which Google Drive folders the Drive tools work in.

  • action='list' (default): the workspace's Drive address, the registered folders (with reachable) and not_added: what is shared with the address but not registered yet.

  • action='add' + link: register a folder, file or Shared Drive the owner shared with the address (a pasted Drive link or id). The first one activates the connection.

  • action='remove' + link: unregister it (the share in Google stays). Not connected yet: channels.connect(channel='google_drive') creates the address to share with.

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_folders"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkNoFor add/remove: a Drive link or id of the shared folder, file or Shared Drive.
actionNoadd or remove; OMIT to list.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

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

The description goes beyond the annotations by disclosing what add/remove actually change and, critically, that removing only unregisters while "the share in Google stays" — direct evidence in support of destructiveHint=false. The one residual tension is that annotations declare readOnlyHint=true while 'add'/'remove' clearly mutate the workspace's folder registry ('The first one activates the connection'); the description makes the behavior unambiguous, so an agent is not misled, but the read-only label is only true of the underlying Google data.

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?

Front-loaded one-line purpose followed by per-action bullets and a short prerequisite note; every sentence carries information about a distinct action or the not-connected state, with 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?

With no output schema, the description compensates by naming what 'list' returns (address, registered folders with 'reachable', and 'not_added') and by explaining the first-add activation path. For a three-parameter, zero-required routing tool this covers everything needed to invoke it correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, and the description adds real meaning on top: it clarifies that 'link' accepts a pasted Drive link or bare id for folder, file, or Shared Drive, and that action should be omitted rather than set to 'list'. It says nothing extra about in_workspace, but the schema already documents that parameter fully.

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 the specific verb and resource ("Manage which Google Drive folders the Drive tools work in") and then enumerates the three concrete actions with their effects, which cleanly separates this configuration/registry tool from data tools such as drive_list or folders_create.

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?

Each action carries its own when-to-use condition: 'list' is explicitly the default when action is omitted, 'add' is for registering a link/id shared with the address (and activates the connection on first use), and 'remove' is for unregistering. It also names the prerequisite alternative channels.connect(channel='google_drive') when the workspace is not connected yet.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.