unegui-mn MCP Server

get_recent_listings

Get the most recent listings from unegui.mn across all categories. Use the optional limit parameter to control how many results are returned (default 20, max 50).

Instructions

unegui.mn нүүр хуудасны хамгийн сүүлийн заруудыг авна.
Get the most recent listings from the unegui.mn homepage.

Args:
    limit: Буцаах зарын дээд тоо / Maximum listings to return
           (default: 20, max: 50)

Returns:
    Бүх ангиллын сүүлийн заруудын JSON.
    JSON with recent listings across all categories.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Without annotations, the description carries the full burden of behavioral disclosure. It does mention that the tool returns JSON across all categories and that limit has a default of 20 and max of 50, but it does not explain ordering guarantees, pagination, error behavior, or authorization needs. This is adequate but not rich.

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 well-structured with Args and Returns sections and is front-loaded with the main purpose. The bilingual text (Mongolian/English) is useful but doubles the length, so it is not maximally concise.

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?

For a simple tool with one parameter and an output schema, the description covers the essential purpose, limit behavior, and return format. It lacks sibling differentiation and notes on ordering or errors, but overall it is sufficiently complete for basic invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The only parameter, limit, is fully explained in the description as the maximum number of listings to return, with default (20) and maximum (50). This adds meaningful meaning beyond the bare schema, which only shows type and default.

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 ('get') and identifies a concrete resource ('the most recent listings from the unegui.mn homepage'). It clearly distinguishes from sibling tools like search_listings, list_categories, browse_category, and get_listing_details by focusing on the homepage's latest listings across all categories.

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

Usage Guidelines2/5

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

No explicit guidance is given about when to use this tool versus alternatives such as search_listings or browse_category. The context of 'homepage' implies a use case, but there are no references to alternatives or exclusions.

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

Deploy Server