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

feishu-user-plugin

by EthanQC
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

reply_message

Reply to a specific text message by its message ID using a bot. Send text replies to any message in Feishu.

Instructions

[Official API] Reply to a specific message by message_id (as bot). Only works for text messages; other types return error 230054.

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>",
      "text": "<text>"
    },
    "name": "reply_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
message_idYesMessage ID to reply to (om_xxx)
textYesReply text

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, the description carries full burden. It discloses that it operates as a bot, only supports text messages, and will return error 230054 for other types. This provides meaningful behavioral context beyond basic operations.

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?

Two sentences, front-loaded with purpose, no redundant text. Every word is informative.

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?

Tool is simple (2 required params, no output schema, no annotations). The description covers purpose and a key limitation; it could optionally mention success return or auth, but is adequate for selection and invocation.

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 descriptions cover 100% of parameters with 'Reply text' and 'Message ID to reply to (om_xxx)'. The tool description adds no additional parameter detail, so 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?

The description clearly states the action ('Reply to a specific message by message_id') and specifies the bot context, distinguishing it from sending new messages or editing. It also notes the text-only limitation, which further clarifies scope.

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?

It implies when to use: to reply to an existing message as a bot. The constraint 'Only works for text messages; other types return error 230054' provides an explicit exclusion for non-text messages, but no alternative tools are suggested.

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