Yenta Directory

Destination overview by name or slug

destination_overview

Read-onlyIdempotent

One call answers what a destination offers and what's on: counts, a few places, next events and guide topics. It counts offers, seasonality and FAQs too, and names the categories and areas listings, events and offers filter by. preview.complete is false when destination_listings / destination_events hold more.

Input Schema

Name	Required	Description	Default
`destination`	Yes	Destination name or slug, e.g. 'Los Cabos'; list_cities names them.

Output Schema

Name	Required	Description	Default
`item`	No
`items`	No
`reason`	No
`sample`	No
`source`	No
`status`	Yes
`pagination`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed29 schema fields changedOct 7, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / destination / description

Previous value: -"Destination name or slug; call search_destinations to discover one."New value: +"Destination name or slug, e.g. 'Los Cabos'; list_cities names them."

addedInput schema / properties / destination / maxLength
```
Added value: +256
```

removedOutput schema / properties / item / anyOf

Removed value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]

removedOutput schema / properties / item / default
```
Removed value: -null
```
removedOutput schema / properties / item / title
```
Removed value: -"Item"
```
addedOutput schema / properties / item / type
```
Added value: +[
+  "object",
+  "null"
+]
```

removedOutput schema / properties / items / anyOf

Removed value: -[
-  {
-    "items": {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]

removedOutput schema / properties / items / default
```
Removed value: -null
```
removedOutput schema / properties / items / title
```
Removed value: -"Items"
```
addedOutput schema / properties / items / type
```
Added value: +[
+  "array",
+  "null"
+]
```

removedOutput schema / properties / pagination / anyOf

Removed value: -[
-  {
-    "additionalProperties": false,
-    "description": "The page a paginated read actually served (FR-13, INV-8).\n\n``next_cursor`` is ``None`` both at the end of the results and when the next\ncursor would exceed ``max_public_cursor`` — in either case there is no\nfurther page a caller can legally request.",
-    "properties": {
-      "cursor": {
-        "title": "Cursor",
-        "type": "integer"
-      },
-      "limit": {
-        "title": "Limit",
-        "type": "integer"
-      },
-      "next_cursor": {
-        "anyOf": [
-          {
-            "type": "integer"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "title": "Next Cursor"
-      },
-      "total": {
-        "title": "Total",
-        "type": "integer"
-      }
-    },
-    "required": [
-      "limit",
-      "cursor",
-      "total"
-    ],
-    "title": "Pagination",
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]

removedOutput schema / properties / pagination / default
```
Removed value: -null
```
addedOutput schema / properties / pagination / type
```
Added value: +[
+  "object",
+  "null"
+]
```

removedOutput schema / properties / reason / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedOutput schema / properties / reason / default
```
Removed value: -null
```
removedOutput schema / properties / reason / title
```
Removed value: -"Reason"
```
addedOutput schema / properties / reason / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / sample / anyOf

Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]

removedOutput schema / properties / sample / default
```
Removed value: -null
```
removedOutput schema / properties / sample / title
```
Removed value: -"Sample"
```
addedOutput schema / properties / sample / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```
removedOutput schema / properties / source / additionalProperties
```
Removed value: -false
```

removedOutput schema / properties / source / description

Removed value: -"FR-13: which approved revision an answer was read from, and how fresh.\n\n``source`` is ``approved-content-revision:<id>`` for every read that answers\nfrom one venue, and the literal ``directory`` for the two cross-venue reads,\nwhich have no single revision to cite."

removedOutput schema / properties / source / properties

Removed value: -{
-  "approved_at": {
-    "anyOf": [
-      {
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "default": null,
-    "title": "Approved At"
-  },
-  "content_version": {
-    "title": "Content Version",
-    "type": "integer"
-  },
-  "powered_by": {
-    "anyOf": [
-      {
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "default": null,
-    "title": "Powered By"
-  },
-  "source": {
-    "title": "Source",
-    "type": "string"
-  }
-}

removedOutput schema / properties / source / required

Removed value: -[
-  "content_version",
-  "source"
-]

removedOutput schema / properties / source / title
```
Removed value: -"SourceReference"
```
removedOutput schema / properties / status / title
```
Removed value: -"Status"
```
removedOutput schema / title
```
Removed value: -"PublicResponse"
```

Changed1 schema field changedSep 23, 2026

addedOutput schema / properties / sample

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

First observedSep 10, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/non-open-world, so safety is covered. The description adds genuinely new behavioral facts the annotations don't carry: results are a partial preview ('a few places'), and truncation is signalled through preview.complete being false when destination_listings/destination_events hold more. That truncation contract is the key thing an agent needs to know.

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?

Two dense sentences with the capabilities front-loaded and zero boilerplate; the truncation caveat sits at the end where it belongs. The middle clause ('It counts offers, seasonality and FAQs too') is list-heavy and slightly redundant with the first sentence, which keeps it from a 5.

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 an output schema present, return values need no explanation, and annotations cover the safety profile. The description covers scope, contents, and the truncation signal — enough for an agent to call it correctly — with only the sibling-selection guidance left implicit.

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?

Only one parameter and schema coverage is 100%; the schema itself documents that it accepts a name or slug and points at list_cities for discovery. The description adds no syntax, format, or resolution-order detail beyond that, so baseline 3 applies.

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 says concretely what the call returns — counts, a few places, next events, guide topics, plus offer/seasonality/FAQ counts and the category/area facets listings, events and offers filter by. That content inventory implicitly distinguishes it from the single-facet siblings (destination_events, destination_offers, destination_seasonality). It never states the core verb+resource as plainly as the title does ('Overview of a destination'), so it lands just short of a 5.

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 'preview.complete is false when destination_listings / destination_events hold more' implies a routing rule: start here for a summary, go to those tools when the preview is truncated. But it's phrased as a return-value note rather than an explicit 'use this tool when…' instruction, and no sibling is named as an alternative for the common case.

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?