Yenta Directory

Search a destination's listings by name

destination_listings

Read-onlyIdempotent

Search a named destination's listings by text, category, area and tags (slugs from destination_facets); optionally near another listing, and the destination's own host calls this search_listings.

Input Schema

TableJSON Schema

Name	Required	Description
`area`	No	Area slug from destination_facets.
`tags`	No	Tag slugs; only listings carrying ALL are returned.
`limit`	No	Maximum number of items to return.
`query`	No	Text to match listing names/descriptions.
`cursor`	No	Number of items to skip; pass `next_cursor` from the previous page.
`category`	No	Category slug from destination_facets.
`language`	No	Language code (e.g. 'en', 'es'); defaults to the destination's.
`radius_km`	No	Search radius in km around near_listing_id; a larger value is reduced to the server maximum.
`destination`	Yes	Destination name or slug; call search_destinations to discover one.
`near_listing_id`	No	A listing id; returns listings within radius_km, nearest first.

Output Schema

TableJSON Schema

Name	Required	Description
`item`	No
`items`	No
`reason`	No
`sample`	No
`source`	No	FR-13: which approved revision an answer was read from, and how fresh. ``source`` is ``approved-content-revision:<id>`` for every read that answers from one venue, and the literal ``directory`` for the two cross-venue reads, which have no single revision to cite.
`status`	Yes
`pagination`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 23, 2026

changedInput schema / properties / query / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 256,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / radius_km / anyOf

Previous value: -[
-  {
-    "minimum": 0,
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 50,
+    "minimum": 0,
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / radius_km / description

Previous value: -"Search radius in km around near_listing_id."New value: +"Search radius in km around near_listing_id; a larger value is reduced to the server maximum."

addedInput schema / properties / tags / maxItems
```
Added value: +8
```

addedOutput schema / properties / sample

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Sample"
+}

First observedSep 10, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds some useful context, such as tag slugs coming from destination_facets and optional proximity search, but it does not disclose pagination behavior or result ordering beyond what the schema already specifies.

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 a single compact sentence that front-loads the core action and enumerates filters efficiently. The trailing clause about the destination's host calling this search_listings is somewhat unclear and adds little value, but overall the structure is tight.

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?

With a rich input schema, output schema, and annotations covering safety, the description is largely complete. It captures the essential search dimensions and facet provenance. It could be stronger on when to choose this over sibling tools, but the available structured metadata fills most gaps.

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%, so the schema already documents all parameters. The description mostly restates the filter categories and facet provenance, adding little beyond the schema. It does not introduce new format, default, or constraint details.

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 clearly states the operation: search a named destination's listings, with explicit filter dimensions (text, category, area, tags) and an optional near-listing mode. This distinguishes it from singular destination_listing and other destination_* siblings.

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 description implies when to use the tool: when you need to search listings for a specific destination. However, it does not explicitly contrast it with alternatives like destination_listing, search, or search_destinations, and the final clause about the destination's host is not actionable guidance.

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

All Yenta Directory tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?