Skip to main content
Glama

get_private_file_url

Read-only

Retrieves a download link for a private QQ chat file using file_id, plus file_hash when the message requires it.

Instructions

获取私聊文件下载链接 使用私聊文件消息段中的 file_id,必要时原样传 file_hash。 Returns: 私聊文件下载链接。

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_id": "<file_id>"
    },
    "name": "get_private_file_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_idYes
user_idNo
file_hashNo

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=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds the useful behavioral nuance that file_hash must be passed verbatim ("原样传") and that the call yields a download link, but says nothing about link expiry, authentication, or rate limits — worth adding for an openWorld tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences plus a return note, front-loaded with the purpose. The closing "Returns:" clause is not redundant here because no output schema exists, and no sentence is wasted.

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 read-only URL retrieval tool with no output schema, the description covers purpose, the source of file_id, hash pass-through, and the return value. The only real gap is the undocumented user_id parameter, which 0% schema coverage leaves entirely to the agent.

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 0%, so the description carries the burden. It explains where file_id comes from and how file_hash should be handled, but leaves user_id completely undefined — despite user_id being part of the schema it is never mentioned, so one of three parameters remains unexplained.

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 states a specific verb and resource ("获取私聊文件下载链接" / get private-chat file download link), and the "私聊" qualifier implicitly separates it from the group/flash URL siblings. It never names an alternative explicitly, but the resource scope alone lets an agent distinguish it.

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?

Usage context is implied rather than stated: the file_id must come from a private-chat file message segment, and file_hash is passed through "as necessary". There is no guidance on when to prefer this over get_group_file_url or get_flash_file_url, nor any stated preconditions or exclusions.

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