Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

kwai_user_posts

Retrieve public posts from a Kwai handle or profile URL, with optional count and cursor pagination. Use it to collect a user's visible Kwai content for analysis or monitoring.

Instructions

kwai: User Posts. GET /v1/kwai/user/posts. Provide one of: handle, url. Get public posts from a Kwai handle or profile URL. Costs 1 credit when it succeeds. Costs 0 credits when posts is empty. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "kwai_user_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoKwai profile URL. Use this or handle.
countNoNumber of posts to return, max 50
cursorNoCursor from the previous response for the next page
handleNoKwai profile handle. Use this or url.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description does real work: it discloses the billing model in detail (1 credit on success, 0 when posts is empty, free for errors, blocked/timeout, invalid requests and cache hits) and even defers not-found charging to the published cost. It still omits auth requirements, rate limits, and pagination behavior despite a cursor parameter.

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?

Front-loaded with endpoint and core action followed by the input constraint, then the cost rules. The billing paragraph is longer than the rest but every clause states a distinct charging outcome and none is redundant.

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

Completeness3/5

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

There is no output schema and no annotations, so the description carries the full burden; it covers cost and sourcing but never describes what a returned post contains or how paging with cursor behaves. For a read tool that returns a list, that is a meaningful gap.

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 100%, so a baseline of 3 applies, but the description adds a genuine constraint beyond the schema: one of handle or url must be supplied, which is not encoded in the schema given that required is empty and each field only says 'Use this or handle'. Count and cursor semantics are left entirely to the schema.

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

Purpose4/5

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

The description states a specific verb and resource ('Get public posts from a Kwai handle or profile URL') and backs it with the literal endpoint GET /v1/kwai/user/posts. It does not explicitly distinguish itself from the sibling kwai_profile tool, so an agent must infer that this returns posts while that returns profile data.

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 line 'Provide one of: handle, url' gives an invocation constraint but no guidance on when to pick this over kwai_profile or the many other *_user_posts siblings. Usage context is implied by the name and resource rather than stated, and there are no when-not conditions.

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