Skip to main content
Glama

send_like

Sends a specified number of likes to a QQ user by user ID, enabling automated profile likes from your QQ account.

Instructions

点赞

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": {
      "user_id": "<user_id>"
    },
    "name": "send_like"
  }
}

Input Schema

NameRequiredDescriptionDefault
timesNo
user_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations already declare a non-read-only, open-world, non-destructive operation; the description adds nothing beyond that — no target scope, no idempotency note (relevant given a `times` parameter), no rate-limit or side-effect information. With zero annotation-adjacent context supplied, the description carries the full behavioral burden and fails it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

Two characters is not conciseness but under-specification; there is no structure and nothing front-loaded. A short description is fine, but every essential fact is missing here.

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

Completeness1/5

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

For a mutating, open-world tool with two undocumented parameters, no output schema, and no annotations explaining targeting, this definition is nowhere near sufficient to call the tool correctly.

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?

Schema description coverage is 0% for 2 parameters. The description does not explain what user_id identifies or why a `times` count (default 1, minimum 0, allowing zero) exists, which is exactly the kind of meaning an agent needs and the schema does not provide.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description "点赞" (like) essentially restates the tool name send_like without adding a specific object or scope. It does not say what is being liked — a message, a user's profile, or a Qzone post — even though siblings such as set_msg_emoji_like, like_qzone, and set_qzone_public_like show the surface is ambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. An agent cannot tell from this text whether send_like is the right tool versus like_qzone or set_qzone_public_like.

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