Skip to main content
Glama

manage_doc_block

Create, update, or delete content blocks in a document. Supports generic blocks, images from local file or token, and file attachments from local file or token.

Instructions

[Official API] Manage content blocks in a document. Single tool replaces v1.3.6 create_doc_block / update_doc_block / delete_doc_blocks. action=create — five modes: (A) Generic — pass children array (e.g. [{block_type:2, text:{...}}]). (B) Image from local file — pass image_path; plugin uploads and patches. (C) Image from token — pass image_token (already uploaded). (D) File attachment from local file — pass file_path; plugin handles VIEW-wrap + replace_file. (E) File from token — pass file_token. action=update — generic (pass update_body), image-replace (pass image_token), or file-replace (pass file_token). action=delete — pass parent_block_id + start_index + end_index (range delete). document_id accepts native ID, wiki node token, or Feishu URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesOperation to perform
document_idYesDocument ID, wiki node token, or Feishu URL (required for all actions)
block_idNoBlock ID — required for action=update.
parent_block_idNoParent block ID — required for create/delete (use document_id for the doc root).
indexNoInsert position for create (optional, appends to end if omitted).
start_indexNoRange start (inclusive) — required for delete.
end_indexNoRange end (exclusive) — required for delete.
childrenNoGeneric blocks for create mode A. E.g. [{block_type:2, text:{elements:[{text_run:{content:"Hello"}}]}}]
image_pathNoLocal image path — create mode B (mutually exclusive with other create modes).
image_tokenNoPre-uploaded docx image token — create mode C, or update image-replace.
file_pathNoLocal file path — create mode D (mutually exclusive with other create modes).
file_tokenNoPre-uploaded docx file token — create mode E, or update file-replace.
update_bodyNoGeneric update payload for action=update. E.g. {update_text_elements:{elements:[{text_run:{content:"new text"}}]}}.
Behavior4/5

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

With no annotations, the description bears full burden. It explains the behavior for each action and mode in detail, but lacks information on side effects, authorization needs, or error handling. Still, it is thorough given the tool's complexity.

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?

The description is well-structured with bullet points and clear sections, front-loading the core purpose. Every sentence adds value, and the length is appropriate for the tool's complexity.

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?

Given the tool's 13 parameters, complex behavior, and lack of output schema, the description covers all actions, modes, and parameter relationships. It provides sufficient information for an agent to use it correctly.

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

Parameters5/5

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

The input schema has 100% coverage, and the description adds significant meaning by grouping parameters into modes, explaining mutually exclusive options, and providing examples. This goes well beyond the schema.

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?

The description clearly states it manages content blocks in a document, replaces three previous tools, and details three actions (create, update, delete) with specific modes. This distinguishes it from sibling tools like create_doc or read_doc.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use each action and mode, including parameter requirements and examples. It explains that it replaces older tools, offering clear context for selection.

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/EthanQC/feishu-user-plugin'

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