Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

drive_share

Shares Google Drive files or folders with people, groups, domains, or anyone via link, assigning access roles like reader, commenter, writer, or owner.

Instructions

Share a file/folder (Doc, Sheet, Slides, anything) with a person, group, domain, or anyone with the link.

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>"
    },
    "name": "drive_share"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNoreader
typeNouser
domainNoFor type domain
emailsNoFor type user/group
fileIdYes
notifyNoSend Google's share notification email
messageNoMessage included in the notification email

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the write/external-effect profile is known from structured data. The description adds nothing beyond that: it never states that this grants access to external principals, whether an existing permission for the same grantee is replaced or added, that notify defaults to sending a Google email, or what permissions are required to share.

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 front-loaded sentence with no filler; the resource scope comes first and the grantee enumeration follows. Nothing is redundant or buried.

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?

For a 7-parameter mutation with 57% schema coverage and no output schema, the description is too thin. An agent cannot tell from it whether the call returns the created permission or shareable link, how `type` interacts with `domain`/`emails`, or what happens on a duplicate share.

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 only 57%, and the description only loosely maps to the `type` enum (person→user, group→group, domain, anyone). It says nothing about `role`, `notify`, `message`, `domain`, or `emails`, nor about the conditional relationship between `type` and those fields, so it fails to compensate for the coverage gap.

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?

The description pairs a specific verb ("Share") with a clear resource ("a file/folder (Doc, Sheet, Slides, anything)") and enumerates the grantee kinds, so an agent immediately knows this grants access. It stops short of naming the sibling drive_update_permission, so the boundary between creating a share and modifying an existing permission is left implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The listing of grantee kinds (person, group, domain, anyone with the link) conveys the supported sharing modes, which is real usage context. However, there is no statement of when to use this versus drive_update_permission or drive_list_permissions, and no prerequisites (ownership rights, whether the caller must already own the file) are given.

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