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

feishu-user-plugin

by EthanQC
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

pin_message

Pin or unpin a chat message by specifying a message ID. Toggle the pinned state to highlight or remove important messages.

Instructions

[Official API] Pin or unpin a message in a chat.

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": "pin_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
message_idYesMessage ID
pinnedNotrue to pin, false to unpin

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.10

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations provided, the description carries full responsibility for disclosing behavioral traits. It only states the action without mentioning potential side effects, permission requirements, reversibility, or response format. For a mutation tool, this lack of behavioral detail is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is one sentence and front-loaded with the action. However, '[Official API]' is an unnecessary prefix that adds no value and slightly clutters the description. Still, it is concise and to the point.

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?

Given the tool's simplicity (2 parameters, no output schema, no annotations), the description provides the core purpose but lacks context about return values, error conditions, or permissions. It is minimally adequate but leaves gaps for an AI agent to make fully informed invocation decisions.

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 covers 100% of parameters with clear descriptions (e.g., 'true to pin, false to unpin'). The description adds no additional parameter-level detail beyond what the schema already provides, so the baseline score of 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 states the tool's function: 'Pin or unpin a message in a chat.' It uses a specific verb ('pin/unpin') and identifies the resource ('a message in a chat'), which distinguishes it from sibling message tools like delete_message or forward_message. The purpose is 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 for pinning/unpinning messages but does not explicitly state when to use it versus alternatives or provide exclusions. No sibling comparison or contextual guidance is given, though the tool's unique action makes the intended usage reasonably clear.

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