Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

drive_list_permissions

Read-only

Lists the people and groups a Google Drive file is shared with by file ID, helping you review who has access.

Instructions

List who a file is shared with.

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_list_permissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds nothing about who counts as 'shared with' (users, groups, domains, anyone-with-link), whether inherited permissions appear, or how large result sets behave on an open-world API.

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 front-loaded sentence with no filler. It is efficient, though its brevity comes at the cost of the missing detail noted elsewhere.

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?

With no output schema, an open-world API, and an undocumented parameter, the description should explain return shape and identifier format. It does neither, leaving an agent to guess at both the input form and the structure of the permissions it gets back.

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% for the single required fileId parameter, so the description is the only place meaning can be added. Saying 'a file' implies the identifier but gives no format guidance (ID vs URL vs path), which is exactly what the bare schema leaves out.

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 ('List who a file is shared with'), making the read-a-permissions-list intent clear and distinguishable from mutation siblings like drive_update_permission. It stops short of naming the resource as 'permissions' explicitly, but an agent can map it without ambiguity.

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 or when-not-to-use guidance. The description does not point to drive_update_permission for changes, drive_share for granting access, or drive_get_file for metadata, even though those siblings sit in the same domain.

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