Skip to main content
Glama
r28ai

Chief of Staff

by r28ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

gdrive_permissions_list

Read-onlyIdempotent

List permissions for a Google Drive file or shared drive to audit access and manage sharing.

Instructions

List a file's or shared drive's permissions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileIdYesThe ID of the file or shared drive.
pageSizeNoThe maximum number of permissions to return. The service may return fewer than this value. If unspecified, at most 100 permissions will be returned for shared drives, and the entire list of permissions for non-shared drives. The maximum value is 100; values above 100 will be coerced to 100.
pageTokenNoThe token for continuing a previous list request on the next page. This should be set to the value of `nextPageToken` from the previous response.
supportsAllDrivesNoWhether the requesting application supports both My Drives and shared drives.
useDomainAdminAccessNoIssue the request as a domain administrator. If set to `true`, and if the following additional conditions are met, the requester is granted access: (1) The file ID parameter refers to a shared drive. (2) The requester is an administrator of the domain to which the shared drive belongs. For more information, see Manage shared drives as domain administrators.
includePermissionsForViewNoSpecifies which additional view's permissions to include in the response. Only `published` is supported.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so safety and idempotency are covered. The description adds nothing about pagination behavior, permission requirements, or what gets returned (e.g., permission objects), which would be valuable context beyond the annotations.

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 zero waste and the core action front-loaded. Appropriate for a simple list operation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter list tool with no output schema and full schema coverage, the description is minimally adequate. It omits useful context such as pagination behavior, the returned data shape, and any auth/domain-admin implications, which an agent might need when calling correctly.

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 documents all six parameters in detail (pageSize limits, pageToken semantics, supportsAllDrives, useDomainAdminAccess, includePermissionsForView). The description adds no parameter-level meaning beyond what the schema provides, so baseline 3 is appropriate.

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 (List) and resource (a file's or shared drive's permissions), which is clear and distinguishes it from sibling write tools like gdrive_permissions_create and gdrive_permissions_delete. It doesn't explicitly name those siblings, but the read-only list scope 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?

No guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. With siblings like gdrive_permissions_create/delete available, an agent gets no routing help beyond the verb 'List'.

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

Deploy Server

Other Tools