Skip to main content
Glama

create_group_file_folder

Creates a new folder in a QQ group's file storage for a specified group, optionally under a parent folder, to organize shared files.

Instructions

创建群文件夹 将 group_id 替换为当前账号可访问的群号。 Returns: { result: { retCode, retMsg }, groupItem: { folderInfo: { folderId, folderName, folderPath, createTime, modifyTime, createUin, modifyUin } } }

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>",
      "name": "<name>"
    },
    "name": "create_group_file_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
group_idYes群号
parent_idNo/

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the agent knows this is a non-destructive write with external visibility; the description is consistent with that. It adds genuine value by spelling out the response envelope ({ result: { retCode, retMsg }, groupItem: { folderInfo: {...} } }), which matters because there is no output schema. It says nothing, however, about failure modes, duplicate-name behavior, or what happens when parent_id does not exist.

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?

The purpose is front-loaded, which is good, and the return-shape block earns its place given the absence of an output schema. But the whole thing is one run-on line mixing Chinese prose with an unformatted JSON-ish dump, and the interleaving makes it harder to scan than a two-part purpose/returns structure.

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?

For a 3-parameter mutation with no output schema, documenting the return envelope and the group access requirement covers the two biggest unknowns. Still missing are the nesting semantics of parent_id and duplicate/validation behavior, which an agent needs to call this correctly on the first try.

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 33% — group_id is documented as "群号" while name and parent_id carry no description at all. The description adds a real constraint for group_id (must be a group the current account can access) but leaves the minLength-1 name semantics and the parent_id "/" root-vs-nested behavior completely unexplained, so it does not compensate for the coverage gap.

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?

"创建群文件夹" states a specific verb (create) and resource (group folder), which cleanly separates it from sibling mutations such as delete_group_file_folder and rename_group_file_folder. The purpose is unambiguous even though the sentence is not in English and lacks any elaboration on what a "群文件夹" contains.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only guidance is "将 group_id 替换为当前账号可访问的群号" (substitute a group number the current account can access), which is an access precondition for one parameter, not a when-to-use rule. There is no statement of when to prefer this over move_group_file or upload_group_file, no mention of whether the folder must not already exist, and no prerequisite/permission guidance beyond group access.

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