Skip to main content
Glama

Get Zola Vendor Details

zola_get_vendor_details
Read-only

Get detailed information about a specific wedding vendor on Zola including pricing, packages, FAQs, reviews, and more. Use the vendor slug from search results.

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": {
      "slug": "<slug>"
    },
    "name": "zola_get_vendor_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe vendor slug (e.g., 'brooklyn-winery', 'stanley-productions-inc'). This is the URL-friendly identifier for the vendor.

Output Schema

NameRequiredDescriptionDefault
faqsNoFrequently asked questions
nameYesVendor business name
slugYesURL-friendly identifier
badgesNoVendor badges and awards
pricingNoPricing information
reviewsNoReview summary
headlineNoShort tagline or headline
locationNoLocation information
packagesNoAvailable packages
vendor_urlNoURL to vendor's Zola page
descriptionNoFull description of the vendor

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 profile is covered. The description adds that the payload covers pricing/packages/FAQs/reviews, which signals breadth of externally sourced data, but says nothing about failure modes for an invalid slug or about rate/concurrency behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with no filler. The capability statement is front-loaded and the operational hint about slug provenance follows immediately.

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 single-parameter read tool with full annotations and an output schema, the definition covers purpose, input provenance, and content scope adequately. The only shortfall is minor: no mention of what happens when the slug is unknown or the vendor does not exist.

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% and the single parameter is fully documented, so the baseline is 3. The description adds genuine value beyond the schema by telling the caller where the slug comes from (search results), which the schema's example values alone do not convey.

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?

States a specific verb and resource ('Get detailed information about a specific wedding vendor on Zola') and enumerates the content categories returned (pricing, packages, FAQs, reviews). It is clearly distinct from the zola_search_vendors sibling by referring to 'search results', though it never names the sibling explicitly.

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 sentence 'Use the vendor slug from search results' implies the correct workflow and prerequisite (first search, then fetch details by slug). There is no explicit statement of when not to use it, nor a named alternative for the case where the caller lacks a slug.

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