Skip to main content
Glama
Sign In
rednote-analyzer-mcp

rednote-analyzer-mcp

by ShellyDeng08
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

rednote_generate_post

Generate a structured RedNote post outline with title, content, hashtags, and tips. Supports tutorial, emotional, review, experience, and casual styles.

Instructions

Generate a RedNote post outline based on topic and style.

Creates a structured post with title, content outline, hashtags, and posting tips. Styles: 干货(tutorial), 情绪(emotional), 测评(review), 经验(experience), casual.

Args: topic: Post topic (e.g., "美股入门", "iPhone 17测评") style: Content style - "干货", "情绪", "测评", "经验", "casual" vertical: Content vertical - "investment", "tech", "lifestyle", "fashion", "general" target_audience: Optional target audience description

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": {
      "topic": "<topic>"
    },
    "name": "rednote_generate_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYes
styleNo干货
verticalNogeneral
target_audienceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.6

TDQS

A4/5.0
Behavior3/5

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

No annotations provided, so description carries the burden. It explains the output and style options but does not disclose behavioral traits like AI usage, creative limits, or error handling.

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 concise, front-loaded with the purpose, and uses clear structure with line breaks and an 'Args' section, making it easy to scan.

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?

With 4 parameters, no output schema, and no annotations, the description covers the essentials: output components, style examples, and parameter explanations. However, it could be more explicit about the output format (e.g., JSON structure).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the description compensates by listing arguments with examples (e.g., '美股入门') and explaining style enums ('干货', '情绪', etc.), adding value beyond the schema's titles and defaults.

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 it generates a RedNote post outline with specific elements (title, content outline, hashtags, posting tips) and distinguishes from sibling tools like rednote_analyze_note and rednote_extract_patterns.

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 the tool is for generating post outlines but does not explicitly state when to use it versus alternatives, nor does it mention exclusions or prerequisites.

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