Skip to main content
Glama
HuntsDesk

Google Workspace MCP VE

by HuntsDesk
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

manage_drive_access

Grant, update, revoke, or transfer ownership of Drive files and folders. Manage permissions for users, groups, domains, or anyone with batch support and optional expiration.

Instructions

Grant, batch-grant, update, revoke, or transfer ownership on a Drive item.

Side effects: all actions mutate permissions; transfer_owner permanently changes the file's owner. Notification emails are sent per send_notification. For read-only inspection use get_drive_file_permissions. Requires the drive.file OAuth scope (or higher for cross-domain transfers).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_google_emailYesThe user's Google email address (authenticated account).
file_idYesDrive file or folder ID.
actionYes"grant", "grant_batch", "update", "revoke", or "transfer_owner".
share_withNoFor "grant" — recipient email (user/group) or domain name (domain). Omit for share_type="anyone".
roleNoFor "grant" (default "reader") and "update": "reader", "commenter", or "writer".
share_typeNoFor "grant": "user", "group", "domain", or "anyone". Default "user".user
permission_idNoRequired for "update" and "revoke". Get it from get_drive_file_permissions.
recipientsNoFor "grant_batch": list of objects with keys email (or domain for domain shares), role, share_type, expiration_time.
send_notificationNoSend the recipient an email. Default True. Applies to grant/grant_batch user/group shares.
email_messageNoCustom body appended to the notification email.
expiration_timeNoRFC3339 deadline ("2026-06-01T00:00:00Z") after which the permission auto-revokes. Applies to grant/update.
allow_file_discoveryNoFor domain/anyone shares, True = indexable in search, False = link-only.
new_owner_emailNoRequired for "transfer_owner". Must be inside the same Workspace domain in most cases.
move_to_new_owners_rootNoAfter transfer, move the file to the new owner's My Drive root. Default False.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed14 schema fields changedv1.0.0
    • changedInput schema / properties / action / description
      Previous value: -"The access management action to perform. Required. One of:\n- \"grant\": Share with a single user, group, domain, or anyone.\n- \"grant_batch\": Share with multiple recipients in one call.\n- \"update\": Modify an existing permission (role or expiration).\n- \"revoke\": Remove an existing permission.\n- \"transfer_owner\": Transfer file ownership to another user."New value: +"\"grant\", \"grant_batch\", \"update\", \"revoke\", or\n\"transfer_owner\"."
    • changedInput schema / properties / allow_file_discovery / description
      Previous value: -"For 'domain'/'anyone' shares, whether\nthe file appears in search. Used by \"grant\"."New value: +"For domain/anyone shares, True = indexable\nin search, False = link-only."
    • changedInput schema / properties / email_message / description
      Previous value: -"Custom notification email message.\nUsed by \"grant\" and \"grant_batch\"."New value: +"Custom body appended to the notification email."
    • changedInput schema / properties / expiration_time / description
      Previous value: -"Expiration in RFC 3339 format\n(e.g., \"2025-01-15T00:00:00Z\"). Used by \"grant\" and \"update\"."New value: +"RFC3339 deadline (\"2026-06-01T00:00:00Z\") after\nwhich the permission auto-revokes. Applies to grant/update."
    • changedInput schema / properties / file_id / description
      Previous value: -"The ID of the file or folder. Required."New value: +"Drive file or folder ID."
    • changedInput schema / properties / move_to_new_owners_root / description
      Previous value: -"Move file to the new owner's My Drive root.\nDefaults to False. Used by \"transfer_owner\"."New value: +"After transfer, move the file to the\nnew owner's My Drive root. Default False."
    • changedInput schema / properties / new_owner_email / description
      Previous value: -"Email of the new owner.\nRequired for \"transfer_owner\"."New value: +"Required for \"transfer_owner\". Must be inside\nthe same Workspace domain in most cases."
    • changedInput schema / properties / permission_id / description
      Previous value: -"The permission ID to modify or remove.\nRequired for \"update\" and \"revoke\" actions."New value: +"Required for \"update\" and \"revoke\". Get it from\nget_drive_file_permissions."
    • changedInput schema / properties / recipients / description
      Previous value: -"List of recipient objects for\n\"grant_batch\". Each should have: email (str), role (str, optional),\nshare_type (str, optional), expiration_time (str, optional). For domain\nshares use 'domain' field instead of 'email'."New value: +"For \"grant_batch\": list of objects with keys email\n(or domain for domain shares), role, share_type,\nexpiration_time."
    • changedInput schema / properties / role / description
      Previous value: -"Permission role -- 'reader', 'commenter', or 'writer'.\nUsed by \"grant\" (defaults to 'reader') and \"update\"."New value: +"For \"grant\" (default \"reader\") and \"update\": \"reader\",\n\"commenter\", or \"writer\"."
    • changedInput schema / properties / send_notification / description
      Previous value: -"Whether to send notification emails. Defaults to True.\nUsed by \"grant\" and \"grant_batch\"."New value: +"Send the recipient an email. Default True.\nApplies to grant/grant_batch user/group shares."
    • changedInput schema / properties / share_type / description
      Previous value: -"Type of sharing -- 'user', 'group', 'domain', or 'anyone'.\nUsed by \"grant\". Defaults to 'user'."New value: +"For \"grant\": \"user\", \"group\", \"domain\", or \"anyone\".\nDefault \"user\"."
    • changedInput schema / properties / share_with / description
      Previous value: -"Email address (user/group), domain name (domain),\nor omit for 'anyone'. Used by \"grant\"."New value: +"For \"grant\" — recipient email (user/group) or domain\nname (domain). Omit for share_type=\"anyone\"."
    • changedInput schema / properties / user_google_email / description
      Previous value: -"The user's Google email address. Required."New value: +"The user's Google email address (authenticated\naccount)."
  2. First observedv1.19.0

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that all actions mutate permissions, transfer_owner permanently changes ownership, and notification emails are sent per send_notification. It also notes the OAuth scope requirement. This provides substantial behavioral context beyond the schema.

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?

The description is composed of five focused sentences, front-loading the core action and then covering side effects, alternatives, and auth requirements. It is efficient but could be slightly more concise by grouping related information.

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's high complexity (14 parameters) and the presence of an output schema, the description provides a solid overview of functionality, side effects, and usage alternatives. It adequately covers the key behavioral aspects, though it could mention handling of different actions more explicitly.

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 baseline is 3. The description does not add additional parameter-level meaning beyond the schema definitions, but it does explain side effects and relationships (e.g., send_notification applies to grant/grant_batch). This is adequate but not exceptional.

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 'Grant, batch-grant, update, revoke, or transfer ownership on a Drive item,' providing a specific verb and resource. It distinguishes itself from sibling tools like get_drive_file_permissions (read-only) by explicitly naming an alternative.

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 offers explicit guidance by stating 'For read-only inspection use get_drive_file_permissions' and mentions the required OAuth scope. However, it does not fully elaborate on when to choose this tool over other mutation tools like set_drive_file_permissions.

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/HuntsDesk/ve-gws'

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