Skip to main content
Glama

qzone_like_list

Read-only

Retrieve the names and QQ numbers of users who liked a QQ Zone 说说 by providing its tid, with optional author and result count.

Instructions

Who liked a 说说 (names and QQ numbers).

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_like_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
tidYes说说 tid
uinNoAuthor of the 说说 (default: you)
countNoMax likers

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?

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds genuine value by disclosing the return contents (names and QQ numbers), but says nothing about pagination, ordering, or how the count limit behaves when more likers exist.

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?

A single short sentence with no wasted wording, and the core purpose is front-loaded. It is terse to the point of being slightly cryptic for readers unfamiliar with the 说说 terminology, but nothing is redundant.

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?

With only three simple parameters, no nested objects, and a 100% covered schema, the definition plus annotations plus the stated return contents cover most of what an agent needs. The absence of pagination or truncation behavior is the main remaining gap for a listing tool.

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 tid, uin, and count are already documented, including the default-author behavior for uin and the count default of 60. The description adds no meaning beyond the schema, which is the expected baseline when the schema is fully annotated.

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 names a specific operation on a specific resource: retrieving who liked a 说说, and it even states the return payload (names and QQ numbers). It does not, however, distinguish this read from write-oriented siblings like set_qzone_public_like or send_like, so an agent must infer the read-only listing nature.

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?

There is no explicit when-to-use guidance, no mention of when not to use it, and no named alternative among the many like-related siblings. The only implied context is that you need a tid, which the schema already requires.

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