Skip to main content
Glama

do_group_album_comment

Posts a comment to a media item in a QQ group album using the group ID, album ID, lloc, and comment content.

Instructions

do_group_album_comment album_id 来自 get_group_album_list;lloc 或视频 id、batch_id 来自 get_group_album_media_list。替换群号及对应资源标识。

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>",
      "lloc": "<lloc>",
      "content": "<content>"
    },
    "name": "do_group_album_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
llocYes
contentYes
album_idYes
group_idYes群号

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false, openWorldHint=true, destructiveHint=false, so the write nature is already known; the description adds nothing about what the write does, what it returns, permission requirements, or idempotency. It also references a "batch_id" parameter that does not exist in the schema, which is confusing rather than informative.

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 at two sentences, but the opening clause merely echoes the tool name and the mixed Chinese/English phrasing makes the instruction harder to parse. The reference to batch_id is dead weight since no such parameter exists.

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 four-required-parameter mutating tool with no output schema and 25% schema coverage, the description should at minimum state the action, clarify what 'content' means, and describe the result. It omits all of these and only covers parameter sourcing.

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 only 25% (just group_id: 群号), so the description must compensate and it partially does, explaining the provenance of album_id and lloc. It leaves the required 'content' parameter entirely unexplained, and mentions a nonexistent batch_id, so the compensation is incomplete.

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

Purpose2/5

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

The description opens by restating the tool name ("do_group_album_comment") and then only explains where parameters come from; it never states the action, e.g. that it posts a comment on a group album media item. The agent must infer the verb+resource from the name alone, and nothing distinguishes it from siblings like comment_qzone.

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?

There is an implied prerequisite chain: album_id must come from get_group_album_list, and lloc/video id from get_group_album_media_list, which is genuinely useful routing information. However, it gives no guidance on when to use this versus the other comment tools, and no conditions or exclusions are stated.

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