Skip to main content
Glama
Google Workspace (GWS) MCP Server

Google Workspace (GWS) MCP Server

drive_permissions_create

Create a Google Drive permission to share a file with users, groups, domains, or anyone by assigning an access role and optional email address.

Instructions

Share a file by creating a permission.

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>",
      "role": "<role>",
      "type": "<type>"
    },
    "name": "drive_permissions_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYesPermission role: owner, organizer, fileOrganizer, writer, commenter, reader
typeYesGrantee type: user, group, domain, anyone
fileIdYesThe file ID to share
emailAddressNoEmail of user/group (required for user/group type)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds no behavioral context beyond that — it does not mention that the grantee may be notified, that repeated calls create duplicate permissions (non-idempotent), or what access is required.

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?

A single seven-word sentence with the effect front-loaded and no filler. It is efficient but so terse that no conditional or scope information is delivered.

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?

This is a non-idempotent mutation with three required parameters, no output schema, and an open-world side effect, yet the description says nothing about permissions needed, notification side effects, or what a successful call returns. The schema carries the parameter burden, but behavioral completeness is lacking.

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 schema already explains role values, grantee type, fileId, and the emailAddress requirement for user/group. The description adds no meaning beyond the schema, which is the expected baseline-3 outcome for full coverage.

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 and resource ("creating a permission") plus its user-facing effect ("share a file"), which is enough to separate it from drive_permissions_list/delete/update by verb alone. It stops short of naming any sibling, so differentiation relies on the agent inferring from the verb.

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?

There is no when-to-use guidance: nothing says when to create a new permission versus calling drive_permissions_update, nor any prerequisite such as needing owner/editor rights or which role to pick. The only implicit cue is the word "share".

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