Skip to main content
Glama

drive_share_link

Read-onlyIdempotent

The web link of a file or folder in the registered Google Drive folders. Changes no permissions: only people who already have access can open it.

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": {
      "file": "<file>"
    },
    "name": "drive_share_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesDrive id or pasted link of a file or folder.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive semantics, and the description adds genuinely new context: despite the 'share' name, it changes no permissions and only reaches users who already have access. That resolves a likely misinterpretation of the tool's effect. It stops short of covering failure behavior for files outside the registered folders.

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?

Two tight sentences, front-loading the return value and following with the permission caveat. No filler or repetition of the schema.

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 two-parameter read tool with full schema coverage and annotations covering safety, the description supplies what an agent needs: what is returned and what side effects do not occur. Only edge behavior (file not in a registered folder) is unaddressed.

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 coverage is 100%, so both parameters are already documented, and the description adds only the scoping phrase 'registered Google Drive folders' that constrains the `file` parameter. It says nothing about `in_workspace` beyond what the schema states.

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?

Names the concrete resource and output ('the web link of a file or folder') and scopes it to registered Google Drive folders, so an agent knows exactly what it retrieves. It does not differentiate itself from siblings such as group_get_invite_link or drive_read, relying instead on the distinctive name.

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 note that only people who already have access can open the link implies when this call is useful (obtaining links for existing collaborators), but there is no explicit when-to-use/when-not guidance and no named alternative for granting access.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.