Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

kwai_profile

Retrieve public Kwai profile information by handle or profile URL to identify and inspect accounts.

Instructions

kwai: Profile. GET /v1/kwai/profile. Provide one of: handle, url. Get public Kwai profile info from a handle or profile URL. Costs 1 credit when it succeeds. 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_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoKwai profile URL. Use this or handle.
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 present, the description carries the full burden and does so in the key area of cost: 1 credit on success, no charge for errors, blocked, timed-out, invalid requests or cache hits, and a qualified note about not-found/empty results. Missing are auth or rate-limit behavior, but the billing disclosure is substantive context an agent cannot get from the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with identity and the parameter constraint, then the cost table, and each sentence carries information. The final not-found sentence is somewhat hedged and wordy ("charged only where that operation's published cost says so") but still earns its place by clarifying an ambiguous billing case.

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 simple two-parameter read tool with no annotations and no output schema, the description covers input selection and the full billing model, which is the main behavioral risk. Returned profile fields are not described, but for a profile lookup those are conventional and the absence of an output schema does not leave the caller unable to invoke it correctly.

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% and both parameters already say "Use this or handle" / "Use this or url," so the description's "Provide one of: handle, url" repeats rather than extends the schema. It does implicitly underscore that at least one identifier is needed despite required being empty, but adds no format or precedence detail beyond that.

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 Kwai profile info") along with the route (GET /v1/kwai/profile). It is clear what the tool does, though it never names or contrasts itself with a sibling; the platform prefix and sibling names like tiktok_profile make the distinction mostly implicit.

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?

It tells the caller they may supply either a handle or a URL, which is a minimum-viable usage constraint. It offers no when-to-use versus when-not-to-use guidance, such as when to prefer this profile lookup over kwai_user_posts or a sibling profile tool, so the agent must infer the choice.

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