Skip to main content
Glama

AgentPay

by io.github.yyxqqq777

List Xiaohongshu user notes

xhs_get_user_notes
Read-onlyIdempotent

List posted notes for a Xiaohongshu user_id (paginated). Returns note summaries and next_cursor for pagination. Use when the user asks for a creator's recent posts. Settles ~0.01 USDC via x402 per page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoPagination cursor from the previous response's next_cursor. Omit or null for the first page.
user_idYesXiaohongshu user ID string from a profile or prior note author.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / properties / cursor / description
      Added value: +"Pagination cursor from the previous response's next_cursor. Omit or null for the first page."
    • addedInput schema / properties / user_id / description
      Added value: +"Xiaohongshu user ID string from a profile or prior note author."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive. The description adds critical behavioral context beyond annotations: the cost 'Settles ~0.01 USDC via x402 per page' and the pagination contract (returns next_cursor). These are not derivable from annotations and are essential for an agent to anticipate side effects and costs.

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 four short sentences, each earning its place: purpose, return content, usage trigger, and cost. It is front-loaded with the primary action, then essential details. No redundant or filler wording.

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

Completeness5/5

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

For a two-parameter, paginated list tool with a rich output schema and annotations covering safety, the description covers all needed call context: purpose, pagination return, usage trigger, and cost. Nothing critical is missing. The output schema exists, so return details are not the description's burden.

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%: both user_id and cursor have thorough descriptions, including the cursor's default and first-page behavior. The description's mention of 'next_cursor' and 'paginated' repeats schema information without adding new parameter-level meaning. Baseline 3 applies because the schema already fully documents parameters.

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 opens with a specific verb and resource: 'List posted notes for a Xiaohongshu user_id'. It explicitly mentions pagination and return format, and distinguishes from the sibling xhs_get_note_detail by focusing on listing rather than single-note detail. The usage hint 'Use when the user asks for a creator's recent posts' reinforces the purpose.

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

Usage Guidelines4/5

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

The description gives an explicit trigger condition: 'Use when the user asks for a creator's recent posts.' It does not explicitly mention when not to use or name alternative tools, but the clear trigger covers the main selection case. A 4 reflects clear context without exclusions or alternatives.

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

All AgentPay toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool has a clearly distinct target: one checks payment configuration, one queries China wholesale prices, and two cover Xiaohongshu note detail vs. user notes. There is no meaningful overlap or risk of an agent confusing one tool for another.

Naming Consistency3/5

The names share a prefix-style convention and use snake_case, but the pattern after the prefix is inconsistent: 'agentpay_payment_status' and 'china_wholesale_pricing_query' are noun-oriented, while both xhs tools are get-prefixed. This is readable and predictable enough, but not a uniform verb_noun convention.

Tool Count5/5

Four tools is within the well-scoped range and each tool earns its place: payment preflight, wholesale sourcing, XHS note detail, and XHS user posts. The set is compact without feeling artificially padded or thin.

Completeness4/5

The server covers its apparent paid-data-access workflows well: agents can verify payment setup, then call the relevant paid lookup tools. Minor gaps exist—there is no XHS search tool, no wholesale supplier-detail endpoint, and no transaction/payment history—but they are workable gaps rather than dead ends.

Resources