Skip to main content
Glama

list_feed

Fetches a batch of pending Bilibili or Douyin items for curation, automatically excluding blocked authors and already judged content, and returns titles, author identities, and links for A/B/C review.

Instructions

拉一批待筛内容(拉黑作者和已判过的自动剔除),返回标题 / 作者身份 / 链接。逐条按 curator://criteria 判 A/B/C。

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": {
      "platform": "<platform>"
    },
    "name": "list_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo条数 1-20,默认 8
keywordNoB站 站内搜索词(可选;不填走推荐流)
platformYes平台

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose non-obvious filtering behavior (blocked authors and already-judged items are removed) and the return fields, which is real value. However, it never says whether pulling a batch marks those items as seen, which matters because reset_seen exists as a sibling; the state side effect of a 'pull' is left unstated.

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?

Two sentences with no filler; the exclusion behavior and the return payload are front-loaded before the follow-up instruction to judge against curator://criteria. The reference to curator://criteria is compact and functional rather than wasteful.

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

Completeness4/5

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

For a three-parameter fetch tool with no output schema, the description covers what comes back (title / author identity / link), what is filtered out, and what to do next. It is slightly incomplete on exhaustion or empty-feed behavior and on the seen-state side effect, but nothing essential for calling it correctly is missing.

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

Parameters3/5

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

Schema description coverage is 100%, with all three parameters (count 1-20 default 8, keyword for Bilibili in-site search vs recommendation feed, platform enum) documented in the schema itself. The description adds nothing parameter-specific beyond the schema. A baseline 3 is appropriate when the schema does the work.

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 names a concrete action and object: it pulls a batch of pending content to be screened and returns title / author identity / link. It also distinguishes the scope from a generic listing by stating that blocked authors and already-judged items are automatically excluded. It does not name a sibling tool, but the fetch-vs-judge split against submit_verdict is implicit.

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 an explicit next step: judge each item A/B/C according to curator://criteria, which tells the agent how this tool fits into the workflow and where the decision rules live. It stops short of stating when NOT to use it or how it relates to alternatives such as get_video_detail or collect_video.

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