Skip to main content
Glama

Search Zola Wedding Vendors

zola_search_vendors
Read-only

Browse and search wedding vendor listings on Zola by type, location, price, and style. Returns vendor profiles with photos, ratings, and pricing. Supports venues, photographers, videographers, florists, bands and DJs, hair and makeup, caterers, cakes and desserts, planners, bar services, officiants, and other services such as attire, dance floors, and floral preservation. Only call this tool if the user is looking to find or compare specific vendors, not for general wedding planning advice.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "vendor_type": "<vendor_type>"
    },
    "name": "zola_search_vendors"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity name to search in (optional)
limitNoNumber of results to return. Always use 8 unless user explicitly specifies a different number (max: 20)
stateNoState code (e.g., 'NY', 'CA') to search in (optional)
offsetNoResults to skip for pagination (max: 200). Always use 0 unless user requests pagination
filtersNoMap of filter keys to arrays of filter values. Available filters vary by vendor_type. Can be null or omitted if no filters are needed. venue filters: - "venue-service-level": ["venue-service-level-all-inclusive", "venue-service-level-limited-services", "venue-service-level-raw-space"] - "venue-setting": ["venue-setting-indoor-space", "venue-setting-outdoor-space", "venue-setting-covered-outdoor-space"] - "target-couple-venue-preference": ["target-couple-venue-preference-farms-barns-ranches", "target-couple-venue-preference-vineyards-wineries", "target-couple-venue-preference-beaches-waterfronts", "target-couple-venue-preference-hotels-inns-resorts", "target-couple-venue-preference-ballrooms-banquet-halls", "target-couple-venue-preference-parks-gardens", "target-couple-venue-preference-historic-estates-mansions", etc.] - "services-offered": ["services-offered-catering-services", "services-offered-bar-services", "services-offered-on-site-accomodations", "services-offered-wheelchair-accessible", "services-offered-pet-friendly", etc.] photographer filters: - "photography-style": ["photography-style-photojournalistic", "photography-style-fine-art", "photography-style-editorial", "photography-style-classic"] - "package-components-services-offered": ["package-components-services-offered-engagement-shoot", "package-components-services-offered-second-shooter", "package-components-services-offered-drone", etc.] - "hours-offered": ["hours-offered-6-hours", "hours-offered-7-hours", "hours-offered-8-hours", "hours-offered-9-hours", "hours-offered-10-hours"] videographer filters: - "videography-style": ["videography-style-cinematic", "videography-style-documentary", "videography-style-storytelling", "videography-style-vintage", "videography-style-classic"] - "videographer-deliverables": ["videographer-deliverables-highlight-reel", "videographer-deliverables-raw-footage", "videographer-deliverables-social-media-sharing", etc.] florist filters: - "florist-service-level": ["florist-service-level-full-service-floral-design", "florist-service-level-a-la-carte", "florist-service-level-wholesale"] - "florist-style": ["florist-style-romantic", "florist-style-modern", "florist-style-bohemian", "florist-style-classic", "florist-style-garden-inspired", "florist-style-alternative-non-traditional"] - "florist-floral-arrangement": ["florist-floral-arrangement-bouquets", "florist-floral-arrangement-centerpieces", "florist-floral-arrangement-ceremony-decor", etc.]
vendor_typeYesType of wedding vendor to search for
target_datesNoTarget wedding dates in ISO 8601 format
max_price_centsNoMaximum price in cents (optional)
min_price_centsNoMinimum price in cents (optional)
max_venue_capacityNoMaximum venue guest capacity (only for venue)
min_venue_capacityNoMinimum venue guest capacity (only for venue)

Output Schema

NameRequiredDescriptionDefault
totalYesTotal number of vendors returned
statusNoWhy there are no vendors: Zola has no location for the city, or more than one place has the name
vendorsYesSummary of matching vendors
search_paramsYesSearch parameters used
location_candidatesNoThe places that match the city, with ambiguous_location

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety and external-data profile is covered. The description adds that results are vendor profiles containing photos, ratings and pricing, which is useful framing. It says nothing about rate limits, result ordering, or what happens when a location filter matches nothing, so the addition beyond annotations is modest.

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?

Purpose and the key call/no-call rule are front-loaded in the first sentence and the closing sentence respectively. The middle vendor-type enumeration is long and partly restates the vendor_type enum, though it does add real meaning for the opaque 'other_services' value (attire, dance floors, floral preservation), so it largely earns its space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 11 parameters, a nested filters object, an output schema and read-only annotations all present in structured fields, the description only needs to carry purpose, scope and routing — and it does. Nothing an agent needs before invoking it is missing.

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% and every parameter, including the nested filters object, is documented in-schema, so the baseline is 3. The description's phrase 'by type, location, price, and style' loosely maps to vendor_type, city/state, min/max_price_cents and filters, but adds no syntax, format, or interaction detail beyond the schema.

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 and resource ('Browse and search wedding vendor listings on Zola') and enumerates the searchable dimensions (type, location, price, style) plus what comes back (photos, ratings, pricing). The final clause distinguishes it from the wedding-advice siblings, so an agent can route correctly without opening any schema.

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?

Gives both a positive condition ('only call this tool if the user is looking to find or compare specific vendors') and a clear exclusion ('not for general wedding planning advice'), which effectively points at zola_search_wedding_advice. It stops short of naming that sibling tool or addressing when to reuse cached results versus re-searching.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources