Skip to main content
Glama

get_group_share_link

Read-only

Generate a shareable link for a QQ group accessible by the current account, usable for invitations or group QR codes. Provide the group ID to create a link others can use to join.

Instructions

获取群分享链接 将 group_id 替换为当前账号可访问的群号。 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": {
      "group_id": "<group_id>"
    },
    "name": "get_group_share_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
src_idNo来源标识(兼容参数)
group_idYes群号
need_short_urlNo是否获取短链接
additional_paramNo附加参数

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish this as a safe read (readOnlyHint=true, destructiveHint=false), and the description adds useful context beyond them: the access precondition on group_id and the fact that the return value is a link usable for invites or as QR-code content. It does not cover rate limits or failure modes, keeping it short of 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.

Conciseness4/5

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

Two compact sentences, front-loaded with the action and then the return value. Slight redundancy between the name restated as '获取群分享链接' and the Returns clause, but nothing extraneous.

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?

There is no output schema, and the description only says the result is a share link, without describing the response shape or whether a short vs. long URL comes back despite need_short_url being a parameter. Adequate for a simple read tool, but not fully complete.

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 100%, so each of the 4 parameters is already documented in the schema; baseline is 3. The description restates the group_id meaning ('群号') without adding new syntax or clarifying need_short_url, src_id, or additional_param.

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+resource (获取群分享链接 / get group share link) that an agent can match to an intent. It lacks any differentiation from near-name siblings such as get_share_link or share_group_ex, so it does not reach a 5.

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?

The sentence '将 group_id 替换为当前账号可访问的群号' gives a real precondition: the group must be reachable by the current account. But it offers no when-to-use framing, no exclusions, and never says how this differs from the other share-link siblings, so guidance is implied at best.

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