Skip to main content
Glama

get_profile_like

Read-only

Retrieve QQ profile like data, including UID, latest like time, like and favorite counts, and user details for analyzing profile interactions.

Instructions

获取资料点赞 Returns: 点赞资料:uid、最近点赞时间、收藏与点赞统计及用户明细。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_profile_like"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo
startNo
user_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is clear. The description adds useful return-content context (uid, recent like time, like/favorite statistics, user details) but says nothing about pagination behavior, ordering, or permissions. With annotations covering safety, a 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the tool purpose and then immediately states the return fields. There is no redundant or filler wording, and every part of the sentence contributes useful information.

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

Completeness2/5

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

For a three-parameter read-only retrieval tool with no output schema and no schema descriptions, the definition is incomplete. It explains what is returned, but not how to control the query through count, start, or user_id, nor when this tool should be chosen over sibling tools.

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

Parameters1/5

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

There are three parameters and schema description coverage is 0%, so the description must compensate, but it never mentions count, start, or user_id. The only related detail is "uid" in the return values, which does not explain the input parameters. An agent cannot determine how to paginate or target a user from this description.

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 gives a clear verb and resource: "获取资料点赞" means retrieve profile likes. It does not distinguish this tool from sibling like-related retrieval tools such as qzone_like_list or get_emoji_likes, so it falls short of a 5.

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 provides no guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. It only states the purpose and return fields, leaving selection entirely to the agent.

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