Get a sample of the newest public adult videos on NudiTok (max 20).
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number (1-based) | |
| cursor | No | Opaque pagination cursor from a prior call | |
| per_page | No | Items per page (max 20) |
| Name | Required | Description | Default |
|---|---|---|---|
| count | No | ||
| videos | No | ||
| has_more | No | ||
| next_cursor | No |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the burden. It does indicate this is a read operation that returns a limited sample of public items, which is useful. However, it does not disclose pagination behavior, result ordering guarantees, authentication needs, or whether cursor and page are mutually exclusive.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence with no filler. The key facts—newest, public, adult videos, sample, max 20—are all front-loaded and easy to parse.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The output schema covers return values, and the input schema covers parameters, but the description omits how page and cursor relate for pagination. An agent could reasonably be unsure whether to supply one, the other, or both, especially given both are optional.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents all three parameters. The description adds only the 'max 20' constraint, which is already present in per_page's schema, so it provides no additional parameter meaning.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the operation as getting a feed of the newest public adult videos on NudiTok, with a maximum of 20 items. This is a specific verb and resource, but it does not explicitly differentiate from siblings like get_trending or search_content.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the tool is for browsing the newest public videos, but it gives no explicit when-to-use guidance or exclusions. It does not mention alternatives such as get_trending for popular videos or search_content for filtered lookup.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
