Skip to main content
Glama
ethancod1ng

RedNote MCP Server

by ethancod1ng

rednote_get_user_notes

Retrieve user notes from Xiaohongshu (Little Red Book) by specifying a user ID, with options for pagination and result limits.

Instructions

获取用户笔记

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYes用户ID
limitNo数量限制
cursorNo分页游标

Implementation Reference

  • The primary handler for the 'rednote_get_user_notes' tool. Validates input parameters, invokes the RedNote API, formats the response as MCP content, and handles errors.
    async getUserNotes(params: any) {
      try {
        validateNotEmpty(params.user_id, 'user_id');
        validateString(params.user_id, 'user_id');
        
        if (params.limit) {
          validateNumber(params.limit, 'limit', 1, 100);
        }
    
        logger.info('Executing get user notes tool', { 
          userId: params.user_id, 
          limit: params.limit,
          cursor: params.cursor 
        });
        
        const result = await this.api.getUserNotes(
          params.user_id, 
          params.limit || 20, 
          params.cursor
        );
        
        return {
          content: [{
            type: 'text',
            text: JSON.stringify(result, null, 2)
          }]
        };
      } catch (error) {
        logger.error('Error in getUserNotes tool:', error);
        return {
          content: [{
            type: 'text',
            text: `Error: ${error instanceof Error ? error.message : 'Unknown error'}`
          }],
          isError: true
        };
      }
    }
  • The input schema and metadata definition for the 'rednote_get_user_notes' tool, used for tool listing and validation.
    rednote_get_user_notes: {
      name: 'rednote_get_user_notes',
      description: '获取用户笔记',
      inputSchema: {
        type: 'object',
        properties: {
          user_id: {
            type: 'string',
            description: '用户ID'
          },
          limit: {
            type: 'number',
            description: '数量限制',
            default: 20,
            minimum: 1,
            maximum: 100
          },
          cursor: {
            type: 'string',
            description: '分页游标'
          }
        },
        required: ['user_id']
      }
    },
  • src/server.ts:64-65 (registration)
    The switch case in the tool request handler that routes calls to the 'rednote_get_user_notes' tool to its implementation.
    case 'rednote_get_user_notes':
      return await this.contentTools.getUserNotes(params);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies a read operation ('获取' - get) but doesn't specify if it's safe (non-destructive), requires authentication, has rate limits, returns paginated results (suggested by the 'cursor' parameter), or what the output format is. For a tool with parameters and no annotations, this leaves significant gaps in understanding its 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 extremely concise with a single phrase ('获取用户笔记'), which is front-loaded and wastes no words. For a simple retrieval tool, this brevity is appropriate, though it may sacrifice clarity. Every part of the description directly states the purpose without redundancy.

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?

Given the tool has 3 parameters, no annotations, and no output schema, the description is incomplete. It doesn't address behavioral aspects (e.g., pagination, safety), usage context, or output details, leaving the agent with insufficient information to invoke it effectively. The high schema coverage helps, but overall context is lacking for a tool with multiple parameters and siblings.

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 schema description coverage is 100%, with clear descriptions for all parameters (user_id, limit, cursor). The description adds no additional meaning beyond the schema, such as explaining how 'cursor' enables pagination or typical use cases for 'limit'. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, but no extra value is provided.

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

Purpose3/5

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

The description '获取用户笔记' (Get user notes) states a clear verb ('获取' - get/retrieve) and resource ('用户笔记' - user notes), providing a basic purpose. However, it lacks specificity about what kind of notes or how they're retrieved, and doesn't distinguish from sibling tools like 'rednote_get_note' (likely for a single note) or 'rednote_search_notes' (likely for broader searches). It's adequate but vague.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a valid user_id), exclusions, or comparisons to siblings like 'rednote_get_note' (for single notes) or 'rednote_search_notes' (for filtered searches). Without such context, an agent might struggle to choose correctly among similar tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ethancod1ng/rednote-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server