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

google-workspace-mcp-advanced

by Skeptomenos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_drive_shareable_link

Retrieve the shareable link for a Google Drive file or folder, including its current sharing status.

Instructions

Gets the shareable link for a Google Drive file or folder.

Args: user_google_email (str): The user's Google email address. Required. file_id (str): The ID of the file or folder to get the shareable link for. Required.

Returns: str: The shareable links and current sharing status.

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": {
      "user_google_email": "<user_google_email>",
      "file_id": "<file_id>"
    },
    "name": "get_drive_shareable_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_google_emailYes
file_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.10

TDQS

A3.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the return value but does not clarify whether obtaining a shareable link might modify sharing settings or require specific permissions. The description also omits any potential side effects, making it insufficient for an agent to anticipate the operation's impact.

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 concise, front-loaded with the primary purpose, and structured with clear Args and Returns sections. Every sentence is informative, with no fluff or redundancy.

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 tool with two string parameters, the description covers the core context: purpose, parameter meanings, and return value. The presence of an output schema reduces the need to detail return structure. However, it lacks explicit behavioral side-effect disclosure and usage context, which prevents a perfect score.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has zero description coverage, and the description compensates by explaining both parameters: 'user_google_email' as the user's Google email address and 'file_id' as the ID of the file/folder. This adds meaning beyond the bare schema fields, although it does not provide format constraints or edge-case behavior.

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 states a clear, specific action: 'Gets the shareable link for a Google Drive file or folder.' This distinguishes it from sibling tools like get_drive_file_download_url (download URL) and share_drive_file (modifying sharing permissions) by focusing on the shareable link concept.

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 description implies usage from its purpose (use this to retrieve a shareable link) but provides no explicit guidance on when to choose it over alternatives. There is no mention of alternatives, exclusions, or contextual prerequisites, leaving the agent to infer based on the tool name and purpose.

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