Skip to main content
Glama

upload_image_to_qun_album

Upload an image to a specified QQ group album using the group ID, album ID, album name, and file path, enabling AI-driven media management.

Instructions

upload_image_to_qun_album album_id 来自 get_group_album_list;lloc 或视频 id、batch_id 来自 get_group_album_media_list。替换群号及对应资源标识。 示例路径位于 SnowLuma 服务端,须替换为该服务可读取的实际文件。

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": {
      "group_id": "<group_id>",
      "album_id": "<album_id>",
      "album_name": "<album_name>",
      "file": "<file>"
    },
    "name": "upload_image_to_qun_album"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYes
album_idYes
group_idYes群号
album_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-destructive, open-world write, so the safety profile is covered. The description adds a genuinely non-obvious operational constraint: the example path lives on the SnowLuma server and must be swapped for a file this service can actually read, which tells the agent the file argument is a server-side path rather than an arbitrary URL. It does not cover size/format limits or failure modes, so not a 5.

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

Conciseness3/5

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

It is short, but it is not front-loaded on purpose or usage and reads as unstructured notes appended to the tool name. The advice about replacing the example path is useful, yet the dangling references to non-existent identifiers cost clarity rather than earning their place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-required-parameter mutation with no output schema and 75% of parameters undocumented in the schema, the description should confirm what album_name means, what the upload affects, and what comes back. It leaves a required parameter entirely undefined and mentions identifiers that don't belong to this tool, so an agent could not reliably construct a call from it alone.

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 only 25%, so the description must carry the load, and it only partially does: album_id's origin and the nature of file are addressed, but the required album_name is never explained anywhere. Worse, it references 'lloc', 'video id' and 'batch_id', none of which exist in this tool's schema, which can send an agent looking for parameters that aren't there.

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

Purpose3/5

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

The name conveys a specific verb+resource (upload an image into a group album), and the description reinforces it by tying album_id/group_id to the album-listing tools. However, the description never states in its own words what the tool does or what it returns, opening with a bare repetition of the tool name and then moving straight into parameter provenance.

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?

Prerequisite workflow is implied by saying album_id comes from get_group_album_list and media identifiers from get_group_album_media_list, which helps an agent sequence calls. But there is no explicit when-to-use versus upload_video_to_qun_album or send_image, and no statement of when this tool should be avoided.

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