coolapk-mcp-pro

Overview Schema Source Related Servers Discussions Admin

coolapk_author_digest

Fetches all high-like posts by a Coolapk author for a chosen topic, ranked by popularity and deduplicated, so you can review the author's full guide series in one call.

Instructions

深挖某作者：一次调用拿到他在指定主题下的全部高赞帖（按热度排序）。

适合发现领域大佬（author_tier=top/expert）后，一次性抓出他关于该主题的完整攻略链（例如「莫离然然」的解锁工具 v1.4→v2.2 全系教程）。内部按 id 去重（置顶帖会跨页重复），关键词空格分隔多词=任一命中。

Args: uid: 作者UID keyword: 主题关键词（空格分隔多词=任一命中），留空返回全部帖子 pages: 抓取页数 1-5，默认 2（约 40 条） top: 返回条数上限，默认 10，最多 50

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": {
      "uid": "<uid>"
    },
    "name": "coolapk_author_digest"
  }
}

Input Schema

Name	Required	Description	Default
`top`	No
`uid`	Yes
`pages`	No
`keyword`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.0Nov 2, 2026

TDQS

A4.3/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 does well: it discloses internal dedupe by id because pinned posts repeat across pages, popularity sorting, OR semantics on multi-word keywords, and the page/size limits (pages 1-5, ~40 items per 2 pages, top max 50). It omits auth requirements and rate-limit behavior, which for a scraping tool is a real gap.

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?

It is front-loaded with the one-sentence value proposition before the usage note and Args list. The worked example earns its space by showing the intended chained-call pattern, though the text is longer than strictly needed.

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 formatting need not be described; combined with the fully documented parameters and the paging, dedupe, and sorting behavior, an agent has everything needed to call it correctly.

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

Parameters5/5

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

Schema description coverage is 0%, but the Args block documents all four parameters with meaning the schema lacks: uid is the author UID, keyword is space-separated with OR semantics and empty-returns-all, pages is capped at 1-5 with a yield estimate, and top defaults to 10 and caps at 50.

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 states a specific verb and resource ('deep-dig an author'), the scope ('all high-like posts under a given topic'), and the ordering rule ('sorted by popularity'), so an agent can distinguish it from a plain feed lister such as coolapk_user_feeds. It does not name the sibling it replaces, which keeps it at 4 rather than 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 says when to use it: '适合发现领域大佬（author_tier=top/expert）后', which routes the agent from coolapk_author into this tool, and gives a concrete scenario ('莫离然然' unlock-tool tutorial chain). It does not state when not to use it or name an explicit alternative tool.

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

Deploy Server