Skip to main content
Glama
pushplus

PushPlus MCP Server

Official
by pushplus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

修改 QQ 机器人配置

open_qqbot_edit

POST /open/qqBot/edit - 修改 QQ 机器人配置。配置编码(qqCode)不允许修改，但需传原值。 请求: id(配置编号,必填), qqName(配置名称,必填), qqCode(原配置编码,必填), sendType(1发给自己/2发到QQ群,可选,默认2), qqGroupId(QQ群编号,sendType=2时必填,取自 groupList 的 id；该群需允许机器人主动消息)…

Instructions

POST /open/qqBot/edit - 修改 QQ 机器人配置。配置编码(qqCode)不允许修改，但需传原值。 请求: id(配置编号,必填), qqName(配置名称,必填), qqCode(原配置编码,必填), sendType(1发给自己/2发到QQ群,可选,默认2), qqGroupId(QQ群编号,sendType=2时必填,取自 groupList 的 id；该群需允许机器人主动消息), botAppId(机器人appId,sendType=1时必填且需已绑定；sendType=2时可不填,以群所在机器人为准)。 统一响应: code(数字,200成功), msg(字符串), data(业务数据)。

Input Schema

NameRequiredDescriptionDefault
idYes配置编号
qqCodeYes原配置编码，不会被修改
qqNameYes配置名称，最多64个字符
botAppIdNo发送使用的机器人appId，sendType=1时必填
sendTypeNo发送类型：1发给自己，2发到QQ群；默认2
qqGroupIdNoQQ群编号，sendType=2时必填，取自 open_qqbot_group_list 的 id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.1.0
    • addedInput schema / properties / botAppId
      Added value: +{
+  "description": "发送使用的机器人appId，sendType=1时必填",
+  "type": "string"
+}
    • addedInput schema / properties / qqCode
      Added value: +{
+  "description": "原配置编码，不会被修改",
+  "type": "string"
+}
    • changedInput schema / properties / qqGroupId / description
      Previous value: -"QQ群编号"New value: +"QQ群编号，sendType=2时必填，取自 open_qqbot_group_list 的 id"
    • addedInput schema / properties / sendType
      Added value: +{
+  "description": "发送类型：1发给自己，2发到QQ群；默认2",
+  "type": "integer"
+}
    • changedInput schema / required
      Previous value: -[
-  "id",
-  "qqName",
-  "qqGroupId"
-]New value: +[
+  "id",
+  "qqName",
+  "qqCode"
+]
  2. First observedv1.0.9

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations the description carries the full burden, and it does disclose key behavior: qqCode is immutable yet must be re-sent, the target group must permit bot-initiated messages, and botAppId must already be bound when sendType=1. Auth/permission requirements and side-effect scope are not covered, 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?

Front-loads the endpoint and purpose, then groups field semantics in one dense but well-ordered block. The redundant 'POST /open/qqBot/edit' path prefix is the only real overhead.

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

Completeness5/5

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

With no output schema and no annotations, the description compensates by documenting the uniform response envelope (code/msg/data) as well as every conditional parameter rule. Nothing an agent needs to invoke this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so baseline is 3; the description goes beyond it by spelling out the sendType-driven requiredness matrix, the provenance of qqGroupId, and the '以群所在机器人为准' override rule for botAppId. That extra conditional logic meaningfully aids correct parameter construction.

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

Purpose5/5

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

States a specific verb+resource ('修改 QQ 机器人配置') and even names the HTTP endpoint, making it unambiguously distinct from siblings like open_qqbot_add, open_qqbot_delete and open_qqbot_list. An agent can identify the operation without opening the schema.

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

Usage Guidelines4/5

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

Gives conditional usage rules (sendType=1 requires botAppId, sendType=2 requires qqGroupId) and points to the sibling source of the group id (groupList 的 id). It never names an explicit alternative for creating vs editing, but the context for correct invocation is clear.

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