Skip to main content
Glama
Sign In
google-workspace-mcp

google-workspace-mcp

by smk-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

drive_file_link_access

Enable temporary link access on an owned Drive file so an external service can download it, then disable access immediately after the fetch.

Instructions

Toggle "anyone with the link" access on a file the account owns.

Built for zero-bandwidth server-side fetches: some APIs (e.g. a
transcription service's source_url parameter) can download a Drive file
themselves — but only while it is link-accessible. Flow: enable, hand the
returned direct_download_url to the fetching service, then IMMEDIATELY
call again with enabled=false to revoke. Never leave link access on.

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": {
      "account": "<account>",
      "file_id": "<file_id>",
      "enabled": "<enabled>"
    },
    "name": "drive_file_link_access"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNoreader
accountYes
enabledYes
file_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.2

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden. It discloses the mutation, the ownership prerequisite, the temporary nature of the access, and the security requirement to always revoke. It could mention side effects on existing link permissions, but the provided safety guidance is substantial.

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?

The description is compact and front-loaded with the core purpose. The flow and warnings are concise, each sentence adds value, and the structure moves naturally from purpose to usage to caution.

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 toggle with no output schema, the description covers the key flow, the returned direct_download_url, and the necessary revocation step. The main missing piece is the 'role' parameter and error/edge-case behavior, but the core context needed to call the tool correctly is present.

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 compensate for the undocumented parameters. It explains the 'enabled' toggle and implies 'file_id' and 'account', but it does not explain the 'role' parameter, which has an enum and default. This leaves a meaningful gap for the agent.

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

Purpose5/5

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

The description uses a specific verb and resource: 'Toggle anyone with the link access on a file the account owns.' This precisely identifies the operation and differentiates it from sharing tools like drive_file_share by focusing on the link-access toggle mechanism.

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

Usage Guidelines4/5

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

The description provides a clear use case: enabling temporary link access for zero-bandwidth server-side fetches, then revoking immediately. It does not explicitly name alternatives or state when not to use the tool, but it gives a strong contextual trigger and a concrete workflow.

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