Skip to main content
Glama

置顶 / 取消置顶一条消息

feishu_pin

Pins or unpins a Feishu group message at the top so key conclusions, specification files, and long-term checklists stay visible for everyone.

Instructions

把一条消息钉在群顶部(公告性质的关键结论),或取消置顶。适合:把最终结论、规范文件、长期有效的清单钉住。

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

Input Schema

NameRequiredDescriptionDefault
unpinNotrue 表示取消置顶,默认 false(置顶)。
message_idYes消息 id(om_ 开头)。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.8/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 mutating nature is known; the description usefully adds the semantic intent (pinning as an announcement/durable reference). It does not mention required permissions, whether there is a cap on pinned messages, idempotency of re-pinning, or whether unpinning removes history — all relevant for a write operation on shared chat state.

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 short sentences: the operation with its scope first, then the qualifying use cases. No filler, no restatement of the title, and the most decision-relevant information is front-loaded.

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 two-parameter tool with full schema coverage and annotations carrying the safety profile, the description covers purpose, both directions of the operation, and typical use cases. Only operational details (permissions, limits, post-pin behavior) are missing, which are secondary at this complexity.

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%, with both message_id format (om_ prefix) and the unpin boolean default already documented in the schema. The description only echoes the pin/unpin duality and adds no new meaning, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a concrete verb and resource — pinning a message to the top of a group chat — and explicitly covers the reverse operation (取消置顶). It does not differentiate itself from nearby siblings such as feishu_chat_announcement, so an agent must infer which mechanism to use for persistent notices.

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 "适合" clause gives concrete usage contexts (final conclusions, spec documents, long-lived checklists), which is clear guidance on when to pick this tool. It stops short of exclusions — nothing says when not to pin (e.g. transient messages) or points to an alternative for announcement-style needs.

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