Skip to main content
Glama

send_qzone_msg

Publish text or image posts to QQ Zone and set visibility for everyone, friends, selected contacts, or yourself. Use it to share updates and control who can view each post.

Instructions

发表说说(QQ 空间,支持纯文字或带图;传 images 自动上传;可设置查看权限) 会发布说说;ugc_right=64 仅自己可见。16/128 还必须提供 target_uins。 Rules: ugc_right must be one of 1, 4, 16, 64, 128; target_uins is required when ugc_right is 16 or 128.

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": {
      "content": "<content>"
    },
    "name": "send_qzone_msg"
  }
}

Input Schema

NameRequiredDescriptionDefault
imagesNo图片数组(可选),支持 file:// http:// base64://;自动上传
contentYes说说正文
ugc_rightNo查看权限:1=所有人可见,4=好友可见,16=部分好友可见,64=仅自己可见,128=部分好友不可见
target_uinsNo权限作用 QQ 号数组;ugc_right=16 时表示可见名单,128 时表示不可见名单

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 only say it is a non-read-only, open-world, non-destructive write. The description adds real context beyond that: images are auto-uploaded and accept file://, http://, and base64:// sources, and ugc_right=64 restricts the post to self only. It stops short of stating what is returned or any rate/spam constraints, so it is strong but not exhaustive.

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?

The core capability and the critical rule are front-loaded in a compact form. It is slightly padded by tautological restatement (会发布说说, ugc_right=64 仅自己可见) and a mid-sentence language/format shift into 'Rules:', which costs a little clarity.

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 4-parameter write tool with no output schema, the definition covers the mode switch, image source formats, and the conditional required parameter. It does not say what the call returns (e.g. post ID) or note any risk of repeated posting, leaving a moderate gap.

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 coverage is 100%, so the schema already documents each parameter and its permission mapping; baseline is 3. The description contributes one genuinely new fact not encoded in the schema — target_uins is required when ugc_right is 16 or 128 — but also wastes lines restating that 64 means self-only.

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?

Description opens with a specific verb+resource: 发表说说 in QQ 空间, with plain-text or image modes and permission control. It clearly separates this from generic messaging siblings (send_msg, send_group_msg) by naming the Qzone surface, though it never explicitly names an alternative.

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 Qzone scope implicitly signals when to pick this over the many send_* messaging siblings, and the 16/128 conditional hints at a prerequisite. But there is no explicit 'use this when / not when' routing statement or mention of a concrete alternative.

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