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

MCP Google Multi-Account Server

by bkbaheti
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

drive_share_file

Share Google Drive files by creating permissions for users, groups, domains, or anyone. Requires confirmation to safely expose the file.

Instructions

Share a Google Drive file by creating a permission. Requires confirm: true as a safety gate since sharing exposes the file to others.

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>",
      "fileId": "<fileId>",
      "type": "<type>",
      "role": "<role>"
    },
    "name": "drive_share_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYesPermission role
typeYesPermission type
domainNoDomain (required for domain type)
fileIdYesThe file ID to share
confirmNoSet to true to confirm sharing
accountIdYesThe Google account ID, alias, or email
emailAddressNoEmail address (required for user/group type)
sendNotificationNoSend notification email (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.3

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and uses it well: it discloses that sharing exposes the file and requires confirm: true as a safety gate. This is valuable behavioral context beyond the schema. It does not detail all side effects, but the most critical safety aspect is articulated.

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 with no filler. The main purpose is front-loaded, and the confirm requirement is a crucial addition. Every word contributes to understanding the tool's function and its key caveat.

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?

Given the tool has 8 parameters and no output schema, the description covers the essential behavioral contract: sharing equates to creating a permission and requires confirmation. The schema handles parameter details. It could mention the return value or consequences, but the current level is adequate for an agent to select and invoke the tool 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. The description adds meaning to the confirm parameter by labeling it a 'safety gate' and tying it to the exposure risk. This goes beyond the schema's simple boolean description, helping the agent understand why confirmation is mandatory.

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 action: 'Share a Google Drive file by creating a permission.' This specifies the verb (share) and resource (Google Drive file) and distinguishes it from siblings like drive_rename_file or drive_update_permissions. The safety gate note adds specificity without confusion.

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?

The description implicitly answers when to use: whenever you want to share a file. It does not explicitly mention alternatives or exclusions, but the action is clear. The confirm requirement also sets a prerequisite, which is useful guidance. However, it does not compare to drive_update_permissions, which could be an alternative for modifying existing permissions.

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