Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

drive_update_permission

Destructive

Change a collaborator's role or revoke their access to a file by setting the permission to reader, commenter, writer, or remove.

Instructions

Change a collaborator's role, or remove their access (role 'remove').

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>",
      "permissionId": "<permissionId>",
      "role": "<role>"
    },
    "name": "drive_update_permission"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYes
fileIdYes
permissionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, openWorldHint=true, so the safety profile is covered. The description's added value is the explicit note that role 'remove' deletes access, reinforcing the destructive path and warning the agent that this is not just a role downgrade. It says nothing about required authorization level or whether the change is reversible, so it stops at a modest supplement.

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?

A single short sentence with the action front-loaded and no padding; the parenthetical is the only elaboration and it earns its place by flagging the destructive enum value.

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?

For a simple three-parameter mutation with a fully enumerated role field and complete safety annotations and no output schema, the definition covers the essential operation. The remaining gap is the provenance and format of permissionId, which would matter for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry the burden of explaining parameters, and it only partially does: it clarifies that role='remove' means revoking access rather than a role assignment. The fileId and especially permissionId (whose source is drive_list_permissions) are never explained, leaving an agent to infer how to obtain them.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (change/remove) and resource (a collaborator's role/access), which is enough for an agent to recognize this as the permission-mutation tool rather than a metadata or sharing tool. It stops short of explicitly naming siblings like drive_share or drive_list_permissions, but the operation itself is unambiguous.

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?

The description implies you use it to modify an existing collaborator, but gives no when-to-use vs drive_share (creating access) or drive_list_permissions (finding a permissionId) guidance, and no prerequisites such as needing owner/editor rights. The only hint is the parenthetical about role 'remove', which is a schema fact rather than usage routing.

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