Skip to main content
Glama
Sign In
xhs-mcp-light

xhs-mcp-light

by tomerose
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

xhs_publish_note

Publish image-text notes to Xiaohongshu with up to 9 images, title, content, and optional tags. Automates browser actions for posting.

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": {
      "title": "<title>",
      "content": "<content>",
      "images": "<images>"
    },
    "name": "xhs_publish_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNo话题标签，如 ["美食", "旅行", "摄影"]。自动去掉 # 号。默认无标签
titleYes标题，最多20个中文字符（超出自动截断）
imagesYes图片路径列表。本地绝对路径或 HTTP URL，最多9张 Windows 示例: ["C:/Users/xxx/Pictures/a.jpg", "C:/Users/xxx/Pictures/b.png"]
contentYes正文内容（纯文本，不含 # 标签）

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description should disclose behavioral traits. It only says 'publish a note', omitting side effects, authentication needs, rate limits, or error conditions. The parameter descriptions cover input rules but not runtime behavior.

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, short sentence with no filler. It is appropriately concise and front-loaded with the core action.

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

Completeness2/5

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

Despite having an output schema and fully described parameters, the description lacks context on authentication, error responses, or typical usage flow. For a mutation tool, this is insufficient for an agent to use it reliably.

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 detailed parameter descriptions (e.g., title truncation, image examples). The tool description itself adds no extra parameter semantics, meeting but not exceeding the baseline.

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 '发布' (publish) and the resource '小红书图文笔记' (Xiaohongshu graphic-text note). It distinguishes itself from sibling tools which are about login and search, not publishing.

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

Usage Guidelines2/5

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

No usage guidance is provided. The description does not mention when to use this tool, prerequisites (e.g., being logged in), or alternatives among siblings. Agents have no context for appropriate invocation.

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