Skip to main content
Glama
dipseth

google-workspace-unlimited

Share Drive Files

share_drive_files

Grant access to Google Drive files by sending invitations to specified email addresses with customizable permissions and optional notification messages.

Instructions

Share Google Drive files with specific people via email addresses

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roleNoPermission role: 'reader' (view only), 'writer' (edit), 'commenter' (comment only)reader
messageNoOptional message to include in the sharing notification email
file_idsYesList of Google Drive file IDs to share
email_addressesYesList of email addresses to share files with
send_notificationNoWhether to send email notifications to shared users
user_google_emailNoUse 'me' or 'myself' for auto-resolution to authenticated user, or provide specific email address. If None, uses current authenticated user (auto-injected by middleware).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
roleYes
errorNo
messageYes
resultsYes
successYes
userEmailYes
totalFilesYes
totalOperationsYes
totalRecipientsYes
failedOperationsYes
sendNotificationYes
successfulOperationsYes
Behavior3/5

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

Annotations indicate mutation (readOnlyHint=false) but description adds no behavioral context beyond 'share'. Does not disclose side effects like email notifications, permission overrides, or auto-resolution of user_google_email. With annotations present, the description is adequate but lacks detail.

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?

One sentence, no redundant information. Front-loaded with core action. Could be slightly longer to cover context, but efficiently structured.

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

Completeness2/5

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

Given 6 parameters and output schema, the description is too minimal. Missing context on behavior (additive sharing, notification sending) and usage scenarios. Output schema exists but is not referenced.

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 coverage is 100% with detailed descriptions. The tool description does not add parameter-level meaning beyond the schema, 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?

The description clearly states the verb (share), resource (Google Drive files), and mechanism (via email addresses), distinguishing it from siblings like 'make_drive_files_public' which makes files public without email sharing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives (e.g., make_drive_files_public). No mention of prerequisites or exclusions.

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/dipseth/google_workspace_fastmcp2'

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