Skip to main content
Glama
Sign In
coolapk-mcp-pro

coolapk-mcp-pro

by yufeng-liang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

coolapk_search

Search Coolapk posts, users, topics, and apps with automatic deduplication, strict keyword filtering, and suspected-ad marking to return relevant community results.

Instructions

搜索酷安社区内容（自动去重 + 严格关键词过滤 + 疑似广告标记）。

Args: keyword: 搜索关键词；多个词用空格分隔，strict 模式下要求全部命中 type: 搜索类型，可选 feed(帖子) user(用户) feedTopic(话题) app(应用) page: 页码 strict: 严格过滤（默认开）：归一化后每个关键词都必须出现在标题/正文/作者名里， 可滤掉酷安搜索混入的不相关结果与机型名单广告；关闭则返回原始结果 sort: 帖子排序，hot(热门，默认)/reply(回复数)/default(综合)。 强烈建议保持默认 hot：酷安默认排序混入大量低互动点评， 实测 hot 直接返回高赞干货帖；结果带 like_num/reply_num 可再筛选

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": {
      "keyword": "<keyword>"
    },
    "name": "coolapk_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
sortNohot
typeNofeed
strictNo
keywordYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and discloses real behavior: automatic deduplication, normalized all-keywords-must-match filtering, ad flagging, and that results carry like_num/reply_num for post-filtering. It omits auth/rate-limit and pagination semantics, which keeps it below 5.

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?

The one-line summary is front-loaded and the Args block is scoped to per-parameter guidance, with little filler. The sort entry is somewhat long relative to its informational value, but every sentence still earns its place.

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

Completeness5/5

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

An output schema exists, so return values need not be defined, and the description still mentions the useful like_num/reply_num fields. For a 5-param search tool with 0% schema coverage, all parameters and the key behavioral quirks are covered.

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

Parameters4/5

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

Schema description coverage is 0%, and the description compensates well: it supplies enum values for type (feed/user/feedTopic/app) and sort (hot/reply/default) that the schema lacks, plus the strict default, while page is only glossed as '页码'. Nearly full compensation, short of complete.

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 first line names a specific verb and resource ('搜索酷安社区内容') and adds differentiating behaviors (dedup, strict keyword filtering, suspected-ad marking). It does not explicitly contrast with siblings like coolapk_suggest or coolapk_feed_detail, so it stops 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 Guidelines4/5

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

It gives concrete when-to-use guidance for parameters: keep strict on to filter irrelevant results and model-list ads, turn it off for raw results, and keep sort=hot because the default Coolapk ordering surfaces low-engagement reviews. It never says when to pick this tool over coolapk_suggest or coolapk_feed_detail, so no explicit alternative routing.

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