Skip to main content
Glama

qzone_post_counts

Read-only

Retrieve view, like, comment, and forward counts for a QQ Zone post by its tid, with optional author uin. Use it to check engagement metrics for a specific 说说.

Instructions

View / like / comment / forward counts of a 说说.

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": {
      "tid": "<tid>"
    },
    "name": "qzone_post_counts"
  }
}

Input Schema

NameRequiredDescriptionDefault
tidYes说说 tid
uinNoAuthor (default: you)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false, and that this is an open-world read, so for safety, the description does not need to repeat those. The description does add that four distinct counters are returned, which is useful context. However, it says nothing about permission or authentication requirements or about what happens when the tid is invalid, so a score of 3 is appropriate.

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?

It is a single front-loaded sentence with no wasted words, and the returned data is stated first. It is terse, but it conveys what the tool returns, and the terseness does not introduce ambiguity.

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 simple two-parameter read tool, the description plus full schema coverage is adequate. The description does not explain the output, which is acceptable because no output schema exists; it only enumerates the counters without their format or nesting.

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%: both tid and uin are documented, including that uin defaults to the caller, so the baseline is 3. The description adds no extra meaning about parameter behavior beyond what the schema already states.

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?

The description of "View / like / comment / forward counts of a 说说" states exactly which metrics it returns, so an agent can distinguish it from siblings such as like_qzone or comment_qzone, which perform actions, whereas this tool reports on them. It lacks a leading verb (for example, "Get") and never names those siblings, so its purpose is clear but not framed against alternatives.

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 description contains no guidance about when to use this tool versus alternatives, no prerequisites, and no exclusions. An agent can infer that it is read-only and that it returns metrics for one post, but it must guess whether the tool is suitable for pre-checking a like or comment count.

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