Skip to main content
Glama

Search Zola Invitations and Paper

zola_search_invitations
Read-only

Search the Zola paper shop for wedding invitations, save the dates, thank-you cards, and other wedding paper, by color, motif, and finish (foil, letterpress, custom photo). Each design links its page on zola.com.

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": {
      "card_type": "<card_type>"
    },
    "name": "zola_search_invitations"
  }
}

Input Schema

NameRequiredDescriptionDefault
foilNoOnly designs with foil
colorsNoColors, for example 'green' or 'dusty blue'. A search without a match gives the available colors
motifsNoMotifs or styles, for example 'floral' or 'barn & country'. A search without a match gives the available motifs
card_typeYesThe kind of card
letterpressNoOnly letterpress designs
custom_photoNoOnly designs with the couple's photo

Output Schema

NameRequiredDescriptionDefault
totalYesNumber of designs that match on zola.com
statusYesno_results when no design matches the filters
designsYesThe matching designs, in the zola.com shop order
card_typeYesThe card type of the search
available_colorsYesColor values for the colors filter
available_motifsYesMotif values for the motifs filter

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=false, so the safety profile is covered. The description adds one useful output behavior — each design links its own zola.com page — but says nothing about result caps, ordering, or pagination, so the added value 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.

Conciseness5/5

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

Two sentences, zero filler. The core capability and its facets are front-loaded, with the link behavior trailing as a secondary detail.

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 full output schema and 100% parameter description coverage, the description need not explain return values or parameter formats. It covers scope and facets adequately; only a note on result limits or the color/motif fallback would make it fully self-sufficient.

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; the description earns a step up by explaining the searchable facet families (color, motif, finish: foil, letterpress, custom photo) and tying card types to the required card_type enum. It still omits the no-match fallback behavior, but that is documented in the schema itself.

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 (Search) plus the precise resource (Zola paper shop: invitations, save the dates, thank-you cards, other wedding paper) and the facets searched (color, motif, finish). The 'paper shop' framing cleanly separates it from siblings like zola_search_registry_products and zola_search_vendors without needing to name them.

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?

Usage is implied by the enumeration of card types and finishes, so an agent can infer this is the catalog-search tool for wedding stationery. However, there is no explicit when-to-use/when-not guidance and no pointer to an alternative when the shopper wants something other than paper goods.

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