Skip to main content
Glama

get_share_link

Retrieves a shareable file-set link by fileset_id for sharing files accessible to the current QQ account.

Instructions

获取文件分享链接 fileset_id 来自 create_flash_task、get_fileset_id 或 list_filesets,替换为当前账号可访问的文件集。

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": {
      "fileset_id": "<fileset_id>"
    },
    "name": "get_share_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileset_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the agent knows this is a non-read network operation. The description adds a permission-scoping constraint (the fileset must be accessible to the current account), which is genuine behavioral context. It says nothing about link lifetime, whether generation is idempotent, or what happens on an inaccessible id.

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?

One compact sentence with the purpose front-loaded and the id-provenance constraint following. Nothing is padded or repeated.

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?

With one parameter, no output schema, and annotations covering the safety profile, the description is close to sufficient for invocation. It still leaves the agent guessing about the returned link's form and validity, and about how this differs from the other share-link tools.

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 0% for the single parameter, so the description must compensate. It does partially, by listing the three tools that produce valid fileset_id values and by implying the value may need to be swapped for one the current account can reach. It does not describe the expected format of the id.

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?

The description names a specific verb and resource ('获取文件分享链接' / obtain a file share link), which is clear on its own. It does not differentiate from related siblings such as get_group_share_link or get_qzone_share_ark, so an agent cannot tell which share-link variant applies from the text alone.

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?

It gives provenance guidance for the required id, naming create_flash_task, get_fileset_id, and list_filesets as sources, and warns that the id must resolve to a fileset accessible to the current account. That is useful prerequisite guidance but not tool-selection guidance: there is no statement of when to use this over the other share-link tools.

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