Skip to main content
Glama

feishu_search_messages

Search messages across Feishu groups using keywords, with optional filters for a specific group or time range.

Instructions

跨群搜索飞书消息(用户身份)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordYes搜索关键词
chat_idNo限定群(可选)
start_timeNo起始时间(Unix 秒)
end_timeNo结束时间(Unix 秒)
Behavior2/5

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

No annotations are present, so the description must fully disclose behavior. It mentions '用户身份' (user identity) but does not clarify authentication requirements, rate limits, result scoping, or handling of empty results. The behavioral information is minimal.

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 description is extremely concise: a single Chinese sentence. It is front-loaded with the core purpose but lacks structure. While efficient, it sacrifices helpful details that could fit without becoming verbose.

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

Completeness2/5

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

Given the tool's complexity (search with multiple optional filters, no output schema), the description is insufficient. It does not explain return format, pagination, or behavior when no results. Complete documentation would require more detail about expected output and edge cases.

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% with descriptions for all 4 parameters (e.g., '搜索关键词'). However, the parameter descriptions are basic and add no additional semantic context beyond the schema fields. The tool description does not elaborate on parameter usage or constraints.

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 '跨群搜索飞书消息(用户身份)' clearly indicates it searches Feishu messages across groups with user identity. It distinguishes from sibling tools like 'feishu_search_user' (user search) and 'feishu_get_messages' (likely single-chat retrieval), but does not explicitly specify whether it searches all accessible groups or requires chat_id.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. Sibling tools are listed but not compared. The optional chat_id parameter implies scope flexibility, but no advice is given on when to search all vs. specific groups.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yoreland/lark-cli-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server