Skip to main content
Glama

forward_qzone_public_feed

Forward a public Qzone feed item to the current account's Qzone feed using the complete entry from get_qzone_public_feeds, with an optional reason; it does not comment or send to QQ contacts.

Instructions

将推荐动态转发到当前账号空间 feed 必须原样取自 get_qzone_public_feeds 的 feeds 数组,不能用旧说说 tid 拼造;示例中的占位字段须整体替换。 只转发,不同时评论或发送给 QQ 联系人。 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": {
      "feed": "<feed>"
    },
    "name": "forward_qzone_public_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
feedYesget_qzone_public_feeds 返回的完整 feeds 条目,保留所有原始 cell 字段
reasonNo转发附言,可为空

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/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 mutation and open-world nature are covered. The description adds genuinely useful behavior context beyond that: the data-integrity constraint that the feed payload must be verbatim from the source array, the placeholder-replacement warning, and the note that unknown fields in the upstream result are preserved.

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 description is compact and front-loads the source-of-truth constraint before the exclusions and return note. Every clause carries operational weight, though the wording is dense and slightly run-on, making it marginally harder to parse than an ideally structured definition.

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

Completeness4/5

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

For a two-parameter mutation with no output schema, the description supplies the essentials: sourcing rule for the required feed object, the optional reason behavior implied by the schema, the exclusion behaviors, and a brief return note preserving unknown fields. Only minor gaps remain, such as failure/permission behavior.

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 100%, so the schema alone already documents both parameters, establishing a baseline of 3. The description adds meaning beyond it by telling the agent that the feed object must be an unmodified source-array entry rather than a hand-built object, which constrains how the parameter may be populated.

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 (转发/forward) and resource (推荐动态 into 当前账号空间 feed), and explicitly limits scope to forwarding only, excluding commenting or sending to QQ contacts. An agent can distinguish it from comment_qzone_public_feed and reply_qzone_public_feed without opening their schemas.

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 a clear precondition: the feed must be copied verbatim from the feeds array of get_qzone_public_feeds and cannot be reconstructed from an old 说说 tid, plus explicit exclusions (no simultaneous comment, no send to contacts). It stops short of naming the alternative tools to use for commenting or messaging, so it is strong but not quite explicit-alternatives level.

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