Skip to main content
Glama

往文档末尾追加正文

feishu_doc_append

Append plain-text paragraphs to the end of an existing Feishu document, ideal for adding content after creating an empty doc. Use it for simple text only; rich formatting is not supported.

Instructions

在已有文档最后追加若干段落(每个字符串一段)。配合 feishu_doc_create 建空文档后往里写。只能追加纯文本段落:加粗、表格、图片、标题层级这些富文本结构目前不支持。要改文档中间的内容请用 feishu_doc_blocks 找到块再处理(尚未开放块级编辑)。

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": {
      "document_id": "<document_id>",
      "paragraphs": "<paragraphs>"
    },
    "name": "feishu_doc_append"
  }
}

Input Schema

NameRequiredDescriptionDefault
paragraphsYes要追加的段落,每个元素一段;空字符串会写成空行。
document_idYes文档 id(docx 链接里 /docx/ 后面那串)。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the write semantics are covered structurally. The description adds genuine behavioral constraints beyond that: append-only at the end, plain text only, and empty strings produce blank lines. It still omits permission requirements, failure behavior, and whether any block identifiers are returned, so it is solid but not rich.

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 the action and scope, then the workflow pairing, then the format limitation and fallback. No filler; every sentence carries a constraint an agent would otherwise get wrong.

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

Completeness4/5

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

For a 2-parameter write tool with no output schema, the definition covers purpose, workflow, format limits and the alternative path, which is close to sufficient. The remaining gap is operational detail (permissions, error/partial-failure behavior, whether appended blocks are addressable afterward).

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% and the schema already explains that document_id is the /docx/ URL segment and that each array element is a paragraph with minItems 1. The description's note that each string is a paragraph restates the schema rather than extending it, so the baseline 3 applies.

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 (append paragraphs to the end of an existing document) and immediately scopes it to plain-text paragraphs only. It also distinguishes itself from feishu_doc_create (build empty doc first) and feishu_doc_blocks (mid-document edits), so an agent can place it without opening sibling schemas.

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?

Explicitly names the workflow (create empty doc with feishu_doc_create, then append) and the exclusion (rich-text structures unsupported; mid-document edits must go through feishu_doc_blocks, which isn't open yet). When-to-use and when-not-to-use are both stated rather than inferred.

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