Feishu IM Message Reading

Pre-execution Notes

All message reading tools in this Skill are called with user identity, and can only read sessions that the user has permission to access

feishu_im_user_get_messages

, either

open_id

chat_id

must be provided (not both)

When
```
thread_id
```
appears in a message, judge whether to use
```
feishu_im_user_get_thread_messages
```
to read thread replies based on user intent
After reading with user identity, if resource markers appear in the message content, use
```
feishu_im_user_fetch_resource
```
to download, which requires
```
message_id
```
+
```
file_key
```
+
```
type
```

Quick Index: Intent → Tool

User Intent	Tool	Required Parameters	Common Optional Parameters
Retrieve historical messages of group/one-on-one chats	feishu_im_user_get_messages	chat_id or open_id (choose one)	relative_time, start_time/end_time, page_size, sort_rule
Retrieve reply messages in threads	feishu_im_user_get_thread_messages	thread_id (omt_xxx)	page_size, sort_rule
Search messages across sessions	feishu_im_user_search_messages	At least one filter condition	query, sender_ids, chat_id, relative_time, start_time/end_time, page_size
Download images in messages	feishu_im_user_fetch_resource	message_id, file_key (img_xxx), type="image"	-
Download files/audio/video in messages	feishu_im_user_fetch_resource	message_id, file_key (file_xxx), type="file"	-

Core Constraints

1. Time Range: Ensure Complete Message Coverage

When the user does not specify a time range explicitly, infer an appropriate

relative_time

based on user intent to ensure the returned messages fully cover the content the user cares about. Use the user-specified value directly when the time is clearly indicated.

2. Pagination: Retrieve More Results as Needed

```
page_size
```
ranges from 1 to 50, default is 50
When
```
has_more=true
```
is returned in the result, use
```
page_token
```
to continue fetching the next page
Judge whether pagination is needed based on user needs: continue pagination when complete results are required, the first page is usually sufficient for overview browsing

3. Thread Replies: Actively Expand Threads to Obtain Context

When retrieving historical messages, if the returned message contains a

thread_id

field, it is recommended to actively fetch the latest 10 replies of the thread (

page_size: 10, sort_rule: "create_time_desc"

) to provide more complete context.

Scenario	Action
Retrieve historical messages and need to understand context (default)	Call `feishu_im_user_get_thread_messages` for detected thread_id to get the latest 10 replies
User requests "complete conversation", "detailed discussion", "check replies"	Fetch all thread replies ( `page_size: 50, sort_rule: "create_time_asc"` ), paginate if necessary
User only browses message overview / User explicitly says not to view replies	Skip thread expansion

Note: Thread messages do not support time filtering (Feishu API restriction), and can only be obtained through pagination.

4. Cross-session Message Search

feishu_im_user_search_messages

supports searching messages across all sessions:

Parameter	Description
`query`	Search keywords, matching message content
`sender_ids`	List of sender open_ids
`chat_id`	Session ID to limit search scope
`mention_ids`	List of open_ids of mentioned users
`message_type`	Message type: file / image / media
`sender_type`	Sender type: user / bot / all (default is user)
`chat_type`	Session type: group / p2p

Each message in the search results additionally includes

chat_id

chat_type

(p2p/group),

chat_name

. One-on-one chat messages also have

chat_partner

(the other party's open_id and name).

5. Extraction of Images/Files/Media Resources

The following resource markers may appear in message content, use

feishu_im_user_fetch_resource

to download:

Resource Type	Marker Format in Content	fetch_resource Parameters
Image	`![image](img_xxx)`	message_id= `om_xxx` , file_key= `img_xxx` , type= `"image"`
File	`<file key="file_xxx" .../>`	message_id= `om_xxx` , file_key= `file_xxx` , type= `"file"`
Audio	`<audio key="file_xxx" .../>`	message_id= `om_xxx` , file_key= `file_xxx` , type= `"file"`
Video	`<video key="file_xxx" .../>`	message_id= `om_xxx` , file_key= `file_xxx` , type= `"file"`

Combine the

message_id

field of the message and the

file_key

in the content to call fetch_resource.

Note: File size limit is 100MB, downloading stickers and resources in cards is not supported.

6. Time Filtering

feishu_im_user_get_messages

and

feishu_im_user_search_messages

support time filtering, while thread messages do not.

Method	Parameter	Example
Relative Time	`relative_time`	`today` , `yesterday` , `this_week` , `last_3_days` , `last_24_hours`
Exact Time	`start_time` + `end_time`	ISO 8601 format: `2026-02-27T00:00:00+08:00`

```
relative_time
```
and
```
start_time/end_time
```
are mutually exclusive and cannot be used at the same time

Available relative_time values:

today

yesterday

day_before_yesterday

this_week

last_week

this_month

last_month

last_{N}_{unit}

(unit: minutes/hours/days)

7. Selection of open_id and chat_id

Parameter	Format	Applicable Scenario
chat_id	`oc_xxx`	Known session ID (applicable to both group chats and one-on-one chats)
open_id	`ou_xxx`	Known user ID, retrieve one-on-one chat messages with this user (automatically parsed to chat_id)

Choose one of the two, priority is given to

chat_id

Usage Scenario Examples

Scenario 1: Retrieve Group Chat Messages and Expand Threads

Step 1: Retrieve group chat messages

json

{ "chat_id": "oc_xxx" }

Step 2: Detect

thread_id

in the returned message, expand the latest thread replies:

json

{ "thread_id": "omt_xxx", "page_size": 10, "sort_rule": "create_time_desc" }

Scenario 2: Cross-session Message Search

json

{ "query": "project progress", "chat_id": "oc_xxx" }

Scenario 3: Retrieve More Messages via Pagination

The first call returns

has_more: true

and

page_token: "xxx"

, continue fetching:

json

{ "chat_id": "oc_xxx", "page_token": "xxx" }

Scenario 4: Download Resources in Messages

json

{ "message_id": "om_xxx", "file_key": "img_v3_xxx", "type": "image" }

Common Errors and Troubleshooting

Error Phenomenon	Root Cause	Solution
Too few message results	Time range is too narrow or time parameter is not passed	Infer an appropriate `relative_time` based on user intent
Incomplete messages	Did not check has_more and paginate	Use page_token to paginate when has_more=true
Incomplete thread discussion content	Did not expand thread_id	Fetch thread replies when thread_id is detected
"open_id and chat_id cannot be provided at the same time"	Passed both parameters	Only pass one of them
"relative_time and start_time/end_time cannot be used at the same time"	Time parameter conflict	Choose one time filtering method
"No one-on-one chat session found with open_id=xxx"	No one-on-one chat record exists	Use chat_id instead, or confirm the existence of one-on-one chat
Empty thread message return	Incorrect thread_id format	Ensure it is in `omt_xxx` format
Image/file download failed	file_key or message_id does not match	Confirm file_key comes from the corresponding message_id
Insufficient permissions	User has not authorized or has no permission	Confirm OAuth authorization is completed and the user is a member of the session

feishu-im-read

NPX Install

Tags

SKILL.md Content (Chinese)

Feishu IM Message Reading

Pre-execution Notes

Quick Index: Intent → Tool

Core Constraints

1. Time Range: Ensure Complete Message Coverage

2. Pagination: Retrieve More Results as Needed

3. Thread Replies: Actively Expand Threads to Obtain Context

4. Cross-session Message Search

5. Extraction of Images/Files/Media Resources

6. Time Filtering

7. Selection of open_id and chat_id

Usage Scenario Examples

Scenario 1: Retrieve Group Chat Messages and Expand Threads

Scenario 2: Cross-session Message Search

Scenario 3: Retrieve More Messages via Pagination

Scenario 4: Download Resources in Messages

Common Errors and Troubleshooting