Skip to main content
Glama
Skeptomenos

google-workspace-mcp-advanced

by Skeptomenos

share_drive_file

Share a Google Drive file or folder with users, groups, domains, or anyone. Set access role, expiration, and notification preferences for secure collaboration.

Instructions

Shares a Google Drive file or folder with a user, group, domain, or anyone with the link.

When sharing a folder, all files inside inherit the permission.

Args: user_google_email (str): The user's Google email address. Required. file_id (str): The ID of the file or folder to share. Required. share_with (Optional[str]): Email address (for user/group), domain name (for domain), or omit for 'anyone'. role (str): Permission role - 'reader', 'commenter', or 'writer'. Defaults to 'reader'. share_type (str): Type of sharing - 'user', 'group', 'domain', or 'anyone'. Defaults to 'user'. send_notification (bool): Whether to send a notification email. Defaults to True. email_message (Optional[str]): Custom message for the notification email. expiration_time (Optional[str]): Expiration time in RFC 3339 format (e.g., "2025-01-15T00:00:00Z"). Permission auto-revokes after this time. allow_file_discovery (Optional[bool]): For 'domain' or 'anyone' shares - whether the file can be found via search. Defaults to None (API default). dry_run (bool): If True, returns a preview and does not create sharing permissions. Defaults to True.

Returns: str: Confirmation with permission details and shareable link.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_google_emailYes
file_idYes
share_withNo
roleNoreader
share_typeNouser
send_notificationNo
email_messageNo
expiration_timeNo
allow_file_discoveryNo
dry_runNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Adds useful context beyond schema: 'When sharing a folder, all files inside inherit the permission', dry_run returns preview, expiration_time auto-revokes. Lacks details on overwrite behavior or permission requirements.

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 summary with clear bullet list for parameters. No fluff, every sentence adds value. Well-organized for quick scanning.

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?

Covers parameters, behavior, and return value. Missing mention of permission overwrite behavior. Nearly complete given output schema exists.

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

Parameters5/5

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

Comprehensive Args section explaining each parameter: share_with options, role default, dry_run purpose, expiration format. Schema coverage is 0% so description fully compensates.

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?

Clear verb-resource pair: 'Shares a Google Drive file or folder' distinguishes from siblings like 'update_drive_permission' (modify) and 'remove_drive_permission' (remove). Includes scope (user, group, domain, anyone).

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 explicit guidance on when to use this tool versus alternatives like 'batch_share_drive_file' or 'update_drive_permission'. Does not mention conditions or prerequisites (e.g., ownership).

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/Skeptomenos/google-workspace-mcp-advanced'

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