Skip to main content
Glama

列群里发过的文件

feishu_chat_files
Read-only

List files shared in a Feishu group chat with message IDs, names, sizes, and send times. Filter by filename keyword and get message IDs needed to recall or delete a file.

Instructions

列出群里发过的文件(对应飞书群聊顶部的「文件」标签页),带消息 id、文件名、大小、发送时间。飞书没有独立的「群文件列表」接口,文件是挂在消息上的,所以这里翻最近的群消息再筛出来。要删某个文件:拿这里的 message_id 去调 feishu_recall。

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": {
      "chat_id": "<chat_id>"
    },
    "name": "feishu_chat_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
pagesNo翻多少页消息,默认 3。
chat_idYes群 id(oc_ 开头)。
keywordNo只留文件名含这个词的(模糊匹配)。
page_sizeNo每页条数,默认 50。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds the important behavioral caveat that there is no dedicated group-file endpoint, so results come from scanning recent messages and are therefore bounded by recency/pagination. It also enumerates the returned fields (message id, filename, size, send time), which the agent needs since there is no output schema. Missing only cost/latency expectations for scanning many pages.

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?

Three short sentences, front-loaded with what is listed and what it returns, then the implementation rationale, then the workflow pointer. No filler or repetition of the schema.

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 no output schema, the description compensates by naming the returned fields, and with only read-only annotations it explains the scan-based retrieval model that limits results. Everything an agent needs to call it correctly and interpret its output is present.

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 coverage is 100%, so chat_id, keyword, pages, and page_size are all documented in the schema itself, including defaults and ranges. The description adds no extra syntax or semantics for these parameters beyond noting message_id is the identifier to reuse with feishu_recall; baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — list files sent in a group chat — and anchors it to the visible Feishu UI ('文件' tab), so an agent knows exactly what data it gets. It also explains the mechanism (files hang off messages, so it scans recent messages) which distinguishes it from a generic drive listing or message search.

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?

Gives clear context for use (finding files shared in a chat) and routes the agent onward for the delete case: take the returned message_id to feishu_recall. It does not state a 'do not use when…' condition, e.g. preferring feishu_drive_list for files stored in a drive folder rather than posted in chat, so it stops short of full exclusion guidance.

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