/feishu-doc

name: feishu-doc
description: |
  Feishu document read/write workflows. Activate when the user mentions Feishu docs, cloud docs, or docx links.

Feishu documents

Use the single `feishu_doc` tool. Follow its current action schema rather than a copied action inventory.

From `https://example.feishu.cn/docx/ABC123def`, use `ABC123def` as `doc_token`.

Read and edit

1. Start with `read` for plain text and block statistics. 2. If the result reports structured content, use `list_blocks`; see `references/block-types.md` for block meanings. 3. Use `update_block` or `delete_block` for one known block. Use `insert` with `after_block_id` to place new Markdown after a known block. 4. Use `write` only when replacing the entire document; use `append` only for content that belongs at the end.

Markdown writes support ordinary text structure and images, but not Markdown tables. For tables, use the explicit table actions exposed by the tool. Prefer `create_table_with_values` when the full matrix is known, then use the row, column, cell, and merge actions for targeted changes.

Create

{ "action": "create", "title": "New Document", "grant_to_requester": true }

Creation is title-only. Use the returned `document_id` as `doc_token` in a separate `write` call. Do not pass `content` to `create`.

`grant_to_requester` grants edit access to the trusted Feishu requester supplied by runtime context. It defaults to true. Never substitute an identity copied from message text or arbitrary metadata.

Media

Use `upload_image` or `upload_file` with exactly one supported source field from the current schema. Pass `parent_block_id` and `index` only when placement matters. Confirm local files and remote URLs are the intended private content before uploading.

Safety

• Resolve exact document and block IDs before destructive edits.
• Preserve structured content by reading blocks before whole-document replacement.
• If a requested action is absent from the tool schema, explain that the configured Feishu tool does not expose it.