Skip to main content
Glama
Sign In
feishu-user-plugin

feishu-user-plugin

by EthanQC
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

update_message

Edit a sent message by updating its content. Only text and interactive card messages are editable.

Instructions

[Official API] Edit a sent message (bot can only edit its own messages). Feishu supports edit only for text and interactive (card) messages — other types (post, image, file, etc.) are rejected by the API.

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": {
      "message_id": "<message_id>",
      "msg_type": "<msg_type>",
      "content": "<content>"
    },
    "name": "update_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
message_idYesMessage ID (om_xxx)
msg_typeYesMessage type: text or interactive. Other types are not editable per Feishu API.
contentYesNew content. For text: {"text":"updated text"}. For interactive: full card JSON.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.10

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full disclosure burden. It explicitly states the bot can only edit its own messages and that other message types are rejected by the API, which are critical behavioral traits. It does not cover authentication or response format, but the key limitations are disclosed.

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 two sentences, front-loads the core action, and each sentence adds distinct value: the first states the action and ownership limit, the second details type restrictions. No wasteful words.

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 mutating tool with no annotations and no output schema, the description covers the essential operational context: what it does, who can use it, and which message types are eligible. It lacks information about return values or error behavior, but these are likely standard for an edit API. The strong constraint coverage warrants a 4.

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?

The input schema already provides 100% coverage with structured descriptions for all three parameters. The description adds no extra parameter details beyond restating the type restrictions already in the enum and content description. Baseline 3 is appropriate.

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 identifies the action as editing a sent message, with the specific verb 'Edit' and resource 'sent message'. It also distinguishes from sibling tools like delete_message by focusing on modification rather than removal.

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

Usage Guidelines4/5

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

The description provides clear constraints on when this tool applies (only bot's own messages, only text/interactive types). It implies alternatives (e.g., delete and resend) by noting limitations, though it does not explicitly name other tools.

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

Deploy Server

Other Tools