Skip to main content
Glama

AgentPay

by io.github.yyxqqq777

Get Xiaohongshu note detail

xhs_get_note_detail
Read-onlyIdempotent

Fetch one Xiaohongshu (小红书) note by share URL or 24-char note_id and return title, description, author, engagement stats, images, and video URL as JSON. Call this when the user pastes an xiaohongshu.com/explore link or a note id. Settles ~0.01 USDC via x402 on each successful call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteYesXiaohongshu note share URL or 24-character hex note_id. Example: https://www.xiaohongshu.com/explore/6a95a1f30000000026019ab7
note_typeNoOptional media hint to speed lookup: image, video, 图文, or 视频.

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 / note / description
      Added value: +"Xiaohongshu note share URL or 24-character hex note_id. Example: https://www.xiaohongshu.com/explore/6a95a1f30000000026019ab7"
    • addedInput schema / properties / note_type / description
      Added value: +"Optional media hint to speed lookup: image, video, 图文, or 视频."
  2. First observed

TDQS

A3.6/5.0
Behavior1/5

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

The description transparently discloses a payment side effect ('Settles ~0.01 USDC via x402 on each successful call'), but this contradicts the idempotentHint annotation: repeated identical calls would incur repeated payments. It also tensions with readOnlyHint, which implies no state-changing side effects. Because the description contradicts the annotations, the score is 1.

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 three focused sentences with no filler: what it fetches, what it returns, when to call it, and the payment detail. Every sentence serves a purpose.

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?

The description covers the input format, output contents, trigger condition, and cost side effect. Since an output schema is present, detailed return-structure documentation is unnecessary, though error handling or failure behavior is not mentioned.

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 clear explanations of both parameters, including examples and the optional note_type hint. The tool description adds little beyond the schema, so it remains at the baseline for high schema coverage.

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 uses a specific verb ('Fetch') and identifies the exact resource (one Xiaohongshu note by URL or 24-char note_id) plus the returned fields. It clearly distinguishes this from sibling tools like xhs_get_user_notes.

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?

It explicitly states when to call the tool ('when the user pastes an xiaohongshu.com/explore link or a note id'), providing clear context. It does not mention when not to use it or alternatives, so it misses the full 'when-not/alternatives' bar.

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

A3.9/5.0
Disambiguation5/5

The four tools target clearly distinct resources: AgentPay status, China wholesale product pricing, Xiaohongshu note details, and a user's note list. Even the two Xiaohongshu tools differ sharply in scope (single note vs. paginated user feed).

Naming Consistency3/5

All names are snake_case, but the verb pattern is inconsistent: agentpay_payment_status has no verb, china_wholesale_pricing_query places 'query' at the end, and xhs_get_note_detail/xhs_get_user_notes follow a verb-after-prefix pattern. Names are readable but not structurally uniform.

Tool Count5/5

With four tools, the server is well-scoped for its stated purpose: one status/readiness tool, one product-pricing search, and two Xiaohongshu content fetch tools. Each tool earns its place and there are no redundant extras.

Completeness4/5

The core surface covers the domain nicely: AgentPay health/status, China pricing lookup, and both note-level and user-level XHS retrieval. A few likely secondary operations are missing, such as an XHS keyword search or a transaction/balance tool, but these are small gaps.

Resources