Skip to main content
Glama

AutoTasker Hub — China Social Data API

search_chinese_social

Cross-board keyword search across Chinese social media trending data. $0.05 USDC per call.

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": {
      "query": "<query>"
    },
    "name": "search_chinese_social"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesSearch keyword (Chinese or English)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does add one genuinely useful operational fact: the $0.05 USDC per-call cost, which lets an agent reason about call volume. It says nothing about read-only semantics, result freshness, pagination, or what a result item contains — gaps that matter for a tool with zero annotation coverage.

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?

Two sentences, zero filler, with the capability stated first and the pricing constraint second. Nothing could be trimmed without losing 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?

No output schema and no annotations mean the description must supply the return-value and safety context, and it does not: an agent cannot tell whether results are trending entries, posts, ranks, or board names, nor what limit does. For a search tool returning unspecified social data, this leaves too much unresolved.

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

Parameters2/5

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

Schema coverage is 50%: query is documented in the schema, but limit (default 10, maximum 20) is undocumented in both schema and description. The description says "cross-board" but never explains what a board is, how many are searched, or that limit caps results — so it does not compensate for the coverage gap.

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?

"Cross-board keyword search across Chinese social media trending data" gives a concrete verb plus resource and scopes the data domain tightly enough to separate it from sibling lookups like baidu_hot or douban_movie. It stops short of naming which boards are covered, so the boundary against other Chinese-social tools stays slightly fuzzy.

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 when-to-use statement, no when-not-to-use statement, and no alternative named. The only usage signal is implicit in the word "trending", leaving the agent to guess whether this is for real-time virality tracking or general keyword lookup.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.