Aisle

Search Wedding Venues

search_venues

Read-onlyIdempotent

Searches published destination wedding venues by country, venue type, guest capacity and price range, optionally leaving out unverified imported listings. Results include descriptions, photos and listing links, with totals and pagination; summary omits descriptions and images. Unknown capacity and unverified imported price bands are null. This search does not check live availability or make bookings.

Input Schema

Name	Required	Description
`type`	No	Venue type filter
`limit`	No	Results per page, from 1 to 50 (default 50).
`offset`	No	Number of results to skip; nextOffset from the previous page continues the result set.
`country`	No	Country name (e.g. "Italy", "Mexico"). A two-letter ISO code ("GR") or the country's own name ("Italia", "España") also works; appliedFilters.country gives the English name matched.
`summary`	No	Return compact comparison fields without descriptions and images (default false).
`price_range`	No	Price range filter: $ (budget) to $$$$ (luxury)
`capacity_max`	No	Upper end of your guest range. Matches venues with a known capacityMin no larger than this; unknown capacity is excluded.
`capacity_min`	No	Lower end of your guest range. Matches venues with a known capacityMax at least this large; unknown capacity is excluded.
`include_unknown_capacity`	No	With capacity_min or capacity_max, also keep venues whose capacity is unknown (null) instead of leaving them out. Most imported listings have no known capacity. Default false.
`exclude_unverified_imports`	No	Leave out unverified imported listings (descriptionStatus "unverified_import"), which carry no description and usually no capacity or price. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 12, 2026

addedInput schema / properties / include_unknown_capacity

Added value: +{
+  "description": "With capacity_min or capacity_max, also keep venues whose capacity is unknown (null) instead of leaving them out. Most imported listings have no known capacity. Default false.",
+  "type": "boolean"
+}

Changed1 schema field changedOct 12, 2026

changedInput schema / properties / country / description

Previous value: -"Country name (e.g. \"Italy\", \"Mexico\")"New value: +"Country name (e.g. \"Italy\", \"Mexico\"). A two-letter ISO code (\"GR\") or the country's own name (\"Italia\", \"España\") also works; appliedFilters.country gives the English name matched."

Changed1 schema field changedOct 11, 2026

addedInput schema / properties / exclude_unverified_imports

Added value: +{
+  "description": "Leave out unverified imported listings (descriptionStatus \"unverified_import\"), which carry no description and usually no capacity or price. Default false.",
+  "type": "boolean"
+}

Changed5 schema fields changedOct 8, 2026

changedInput schema / properties / capacity_max / description

Previous value: -"Maximum guest capacity needed"New value: +"Upper end of your guest range. Matches venues with a known capacityMin no larger than this; unknown capacity is excluded."

changedInput schema / properties / capacity_min / description

Previous value: -"Minimum guest capacity needed"New value: +"Lower end of your guest range. Matches venues with a known capacityMax at least this large; unknown capacity is excluded."

addedInput schema / properties / limit

Added value: +{
+  "description": "Results per page, from 1 to 50 (default 50).",
+  "maximum": 50,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / offset

Added value: +{
+  "description": "Number of results to skip; nextOffset from the previous page continues the result set.",
+  "maximum": 100000,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / summary

Added value: +{
+  "description": "Return compact comparison fields without descriptions and images (default false).",
+  "type": "boolean"
+}

First observedOct 2, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world. The description adds real value beyond them: what the results contain (descriptions, photos, links, totals, pagination), how summary mode differs, and the null semantics for unknown capacity and unverified price bands, plus an explicit statement that no booking/availability side effects occur.

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?

Three dense sentences, front-loaded with the core search action and filters before result shape and limitations. Every sentence carries information, though the null/import clauses are somewhat compressed into one long sentence.

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 no output schema, the description usefully covers the return shape (descriptions, photos, links, totals, pagination) and the summary variant. All ten parameters are documented in the schema, and the no-booking limitation is stated, so little is missing for correct invocation.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema lacks: 'Unknown capacity and unverified imported price bands are null' clarifies the result-side semantics of the capacity/price filters, and the summary clause explains the summary flag's effect on payload contents.

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?

States a specific verb (Searches) and resource (published destination wedding venues) with the exact filter dimensions (country, type, capacity, price). It is easily distinguished from siblings like search_vendors, search_guides and list_venue_countries.

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

Usage Guidelines4/5

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

The closing sentence gives a clear boundary ('does not check live availability or make bookings'), and the mention of optionally excluding unverified imports signals intent. However it never explicitly routes the agent between this and sibling tools such as search_vendors or get_venue_details.

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

All Aisle tools Inspect

Try in Browser

Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?