Google Workspace (GWS) MCP Server

drive_permissions_proposeOwnershipTransfer

Propose transferring Drive file ownership to another user, setting them as pending owner. The recipient must accept to complete the transfer.

Instructions

Propose transferring ownership of a file between personal/consumer Google accounts (use drive_permissions_transferOwnership instead for a same-organization Workspace transfer, which completes immediately). Google Workspace ownership cannot be transferred to an account outside the organization. This does NOT transfer ownership by itself: it sets role=writer + pendingOwner=true, and the prospective owner must separately accept by setting role=owner + transferOwnership=true on their own permission, under their own credentials. Google sends the recipient a notification email that cannot be disabled; nothing changes for the current owner unless and until they accept. Only individual users can be proposed — not groups, domains, or service accounts (service accounts have no Drive storage quota and the transfer will fail). Ownership transfers are not supported for files in shared drives.

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": {
      "fileId": "<fileId>",
      "emailAddress": "<emailAddress>"
    },
    "name": "drive_permissions_proposeOwnershipTransfer"
  }
}

Input Schema

Name	Required	Description
`fields`	No	Fields to return (e.g. "id,role,type,pendingOwner")
`fileId`	Yes	The file to propose transferring
`emailAddress`	Yes	Email address of the prospective new owner (an individual user)

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.4.1Sep 24, 2026

TDQS

A4.9/5.0

Behavior5/5

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

The description goes far beyond the annotations by disclosing that this tool does not complete the transfer itself, that it sets role=writer + pendingOwner=true, and that the recipient must separately accept. It also warns about the non-disableable notification email and that nothing changes for the current owner until acceptance. This is rich behavioral context beyond the readOnlyHint=false and destructiveHint=false annotations, with no contradiction.

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 long but every sentence carries essential operational or scoping information. It front-loads the primary purpose and the sibling alternative, then layers behavioral caveats and exclusions in a logical order. There is 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?

For a nuanced ownership-transfer tool, the description covers when to use it, how the underlying API behavior works, required recipient action, email side effects, and all major unsupported cases. No output schema exists, but the description sufficiently explains the tool's behavior for correct invocation.

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 description coverage is 100%, so the baseline is 3. The description adds useful semantic context for parameters: emailAddress must be an individual user (not groups, domains, or service accounts) and fileId cannot refer to a file in a shared drive. This goes beyond the schema's short descriptions.

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 states a specific verb and resource: proposing an ownership transfer of a Drive file, and explicitly distinguishes it from the sibling drive_permissions_transferOwnership. It also clarifies the personal/consumer account scope, leaving no ambiguity about what the tool does.

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?

The description explicitly says to use drive_permissions_transferOwnership for same-organization Workspace transfers that complete immediately. It also provides clear exclusions: no transfers to accounts outside a Workspace organization, no groups/domains/service accounts, and no shared drive files. An agent knows exactly when to use this tool versus the alternative.

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

Deploy Server