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

coolapk-mcp-pro

by yufeng-liang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

coolapk_user_feeds

Fetches posts published by a Coolapk user across multiple pages, with keyword filtering and sorting by interaction heat or publish time for focused profile research.

Instructions

查看酷安用户发布的帖子（支持多页聚合、关键词过滤与热度排序）。

Args: uid: 用户UID page: 起始页码（pages>1 时从该页开始连续抓取） pages: 连续抓取页数 1-5，默认 1；想看某作者的历史干货时设 2-3 keyword: 只保留标题或正文含该词的帖子（空格分隔多词=任一命中） sort: 排序，default(接口原始顺序) / hot(互动热度) / latest(发布时间)

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_user_feeds"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYes
pageNo
sortNodefault
pagesNo
keywordNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose meaningful behavior: pages>1 fetches consecutive pages starting at `page`, and space-separated keywords use OR matching. It omits auth requirements, rate limits, and failure behavior when a page range exceeds available data.

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?

Front-loaded one-line summary followed by a tight per-argument list; each line adds distinct information and nothing is repeated from the schema titles. The mixed prose/Args format is slightly verbose but well organized.

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?

With 5 parameters at 0% schema coverage, the description fully compensates by documenting every argument's meaning, defaults, and bounds. An output schema exists, so return values need not be explained, and the aggregation semantics that an agent must reason about 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 coverage is 0%, so the description must supply all parameter meaning — and it does: uid, page as the start page for aggregation, pages bounded to 1-5 with a default, keyword with multi-term OR semantics not present in the schema, and sort with its three concrete values (default/hot/latest) where the schema has a bare string with no enum.

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?

States a specific verb+resource (查看酷安用户发布的帖子) and enumerates the capabilities it supports (multi-page aggregation, keyword filter, hotness sort), so an agent knows exactly what it retrieves. It does not, however, distinguish itself from siblings like coolapk_search or coolapk_author_digest, which also surface author content.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the pages arg note '想看某作者的历史干货时设 2-3' gives one concrete scenario, and the keyword/sort notes hint at filtering intent. There is no explicit when-to-use-this-vs-alternative routing against coolapk_search, coolapk_author_digest, or coolapk_feed_detail.

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