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

feishu-user-plugin

by EthanQC
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

send_as_user

Send a text message as the logged-in Feishu user, with optional reply threading and real @-mentions that trigger push notifications.

Instructions

[User Identity] Send a text message as the logged-in Feishu user. Supports reply threading and real @-mentions (triggers push notifications).

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": {
      "chat_id": "<chat_id>",
      "text": "<text>"
    },
    "name": "send_as_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
chat_idYesTarget chat ID. Numeric (from create_p2p_chat / search) preferred; oc_xxx is auto-resolved via getChatInfo + cookie search since v1.3.7 (C1.4).
textYesMessage text. If `ats` is provided, include the display marker for each @ in this text (default marker is `@<name>`).
atsNoOptional @-mentions. Each entry: {userId: "ou_xxx", name: "DisplayName"}. The text must contain each @<name> marker in order — it gets spliced into a real AT element so the mentioned user receives a notification.
root_idNoThread root message ID (for reply, optional)
parent_idNoParent message ID (for nested reply, optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.10

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds valuable context about @-mentions triggering push notifications and the 'as user' identity aspect. However, it does not mention side effects like message irreversibility, delivery guarantees, or prerequisites such as login status. Some behavioral traits are disclosed, but not comprehensively.

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 a single, information-dense sentence preceded by a useful identity tag. It states the core action first, then qualifying details (reply threading, @-mention behavior). Every word earns its place; there is no fluff or repetition.

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

Completeness3/5

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

The tool has 5 parameters, no output schema, and no annotations. While the description and schema together cover the mechanics, the description lacks guidance on choosing this vs closely related siblings (send_to_user, send_to_group, reply_message) and does not hint at return values or failure conditions. It is adequate for a simple send action but leaves contextual gaps given the tool's position among many similar send variants.

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 description coverage is 100%, so the parameters (chat_id, text, ats, root_id, parent_id) are already well-documented in the schema. The description adds minimal param value beyond noting that @-mentions are 'real' and trigger notifications, which slightly augments the schema's explanation. Baseline 3 is appropriate given the schema's thoroughness.

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 ('Send a text message') and the actor ('as the logged-in Feishu user'), immediately distinguishing it from bot-send alternatives. Mention of 'text message' and 'real @-mentions' differentiates it from sibling tools like send_post_as_user, send_card_as_user, and send_message_as_bot. The verb+resource structure is specific and unambiguous.

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

Usage Guidelines3/5

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

The description implies usage contexts through phrases like 'as the logged-in Feishu user' (vs bot) and 'Supports reply threading' (vs standalone send), but it does not explicitly state when to choose this over alternatives like send_to_user, send_to_group, or reply_message. No exclusions or direct comparisons are provided, leaving the agent to infer selection criteria.

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