rednote-gate
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RN_SITE | No | `xiaohongshu.com` (mainland accounts) or `rednote.com` (overseas accounts). | from `npm run login` |
| RN_NOTIFY | No | `0` turns off Mac notifications. | on |
| RN_DRY_RUN | No | `0` lets the worker click the final button on approved items. | 1 |
| RN_DATA_DIR | No | Queue, ledger, screenshots, lock. | <repo>/data |
| RN_HEADLESS | No | `1` runs Chromium headless. | headed |
| RN_DAILY_LIKES | No | Live likes allowed in any rolling 24 hours, separate from `RN_DAILY_WRITES`. | 10 |
| RN_TYPE_MAX_MS | No | Longest delay per typed character. | 140 |
| RN_TYPE_MIN_MS | No | Shortest delay per typed character. | 40 |
| RN_DAILY_WRITES | No | Live attempts allowed in any rolling 24 hours. | 5 |
| RN_SESSION_PATH | No | Saved login session. | <repo>/.session/state.json |
| RN_APPROVAL_PORT | No | Approval page port. | 7317 |
| RN_OPEN_APPROVAL | No | `0` stops the approval page opening by itself. | on |
| RN_COMMENT_GAP_MIN | No | Minutes between live comment or reply attempts. | 10 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| rednote_login_statusA | Check whether the saved RedNote session is logged in (main site and creator site). Read only. |
| rednote_searchB | Search RedNote notes by keyword. Read only. Returns note urls that carry the xsec_token other tools need. |
| rednote_get_noteB | Read one note: title, body, author, tags, counts. Read only. |
| rednote_get_commentsA | Read the first page of comments on a note: id, author, text. Read only. Use these values for rednote_reply_comment. |
| rednote_my_notesA | List the logged-in account's own notes, newest first: noteId, title, likes, url. Read only. Use the url for comments and replies on your own notes. |
| rednote_create_postA | Queue a photo note for human approval. Does NOT post. Returns a queue id. |
| rednote_create_draftA | Queue a photo note to be saved as a draft, after human approval. Does NOT post. Returns a queue id. |
| rednote_create_video_postA | Queue a video note for human approval. Does NOT post. One MP4 or MOV, absolute path, up to 500 MB. RedNote processes the video after upload, which can take minutes. |
| rednote_like_noteA | Queue a like on a note for human approval. Does NOT like it yet. Likes have their own daily cap (10 by default). Pass noteTitle so the human sees which note. |
| rednote_post_commentA | Queue a comment on a note for human approval. Does NOT post. Returns a queue id. |
| rednote_reply_commentA | Queue a reply to one comment for human approval. Does NOT post. Pass commentId, commentAuthor and commentText exactly as rednote_get_comments returned them. |
| rednote_open_approval_pageA | Open the approval page in the user's browser so they can approve or reject queued writes. Returns no link. |
| rednote_make_cardsA | Render text-card images (1080x1440 PNG, RedNote's 3:4) on this computer, for notes without photos. Never touches RedNote. Returns absolute paths to pass as images to rednote_create_post. Card 1 is the cover: a short title (use \n to break a Chinese title where it reads best) and 0 to 2 lines; later cards carry up to 8 short lines. |
| rednote_helpA | What rednote-gate can do: every tool and prompt, the current mode, and what is left of today's budget. Never touches RedNote. |
| rednote_queue_statusB | List recent queued writes and what happened to them. Read only. Never touches the browser. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| post_photos | Write a RedNote photo note from your photos and a short brief, then queue it for your approval. |
| post_from_concept | Research a concept on RedNote, write a note about it, make text-card images, and queue it for your approval. |
| reply_to_comments | Read the comments on one of your notes, draft replies to the ones worth answering, and queue them for approval. |
| research_topic | Search a topic, read the top notes and their comments, and summarise what works. Read only. |
| help | Every tool and prompt, your current mode, and what is left of today's budget. |
| review_queue | Summarise the approval queue and recent results, and open the approval page. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Most tools target a clearly distinct resource+action (search vs get_note vs my_notes, post_comment vs reply_comment). The main source of overlap is create_post vs create_draft vs create_video_post, but the descriptions clarify the photo/draft/video distinctions. An agent can reliably pick the right tool.
All tools share the rednote_ prefix and use snake_case, with a mostly predictable verb_noun pattern (get_note, create_post, reply_comment). Minor deviation: status tools are noun-first (login_status, queue_status, my_notes), but this reads consistently as a status/list category.
15 tools is well within the ideal range and each one earns its place across read, queued-write, approval, and support operations. No redundant or filler tools are present.
Covers the core lifecycle: login check, search, read note/comments, own-note listing, and queued publish/draft/video/like/comment/reply with a human-approval flow and card rendering. A few gaps exist (no unfollow/delete/update note, no user-profile or notification reads), but core workflows are workable.