Skip to main content
Glama

Search Zola Help Center Guides

zola_search_help_articles
Read-only

Use this when the user asks how a Zola product or service works. Zola's general help articles from the Zola Help Center, about Zola's own products and services: the registry, gift orders and shipping, cash funds and fees, the wedding website, invitations and paper orders, the guest list, the vendor marketplace, and the Zola account. Not for general wedding advice. Do not use for the state of the couple's own orders, gifts, cash fund or store credit: use zola_get_my_order_history, zola_get_my_gift_tracker, zola_get_my_cash_fund_status or zola_get_my_credits.

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": {
      "query": "<query>"
    },
    "name": "zola_search_help_articles"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesThe question about Zola, for example 'How do guests ship a gift to my address?'

Output Schema

NameRequiredDescriptionDefault
statusYesno_results when the help center has no answer for the question
resultsYesThe best help articles, best first
help_center_urlYesThe Zola Help Center

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/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 a useful content boundary that annotations cannot express (static Zola-owned help content, not general wedding knowledge). It does not describe result volume, ranking, or pagination, but an output schema exists to carry return-shape detail.

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?

Front-loaded with the when-to-use trigger and exclusions before the topic inventory, which is the right order for an agent. The topic list is long and slightly repetitive ('Zola's general help articles from the Zola Help Center, about Zola's own products and services'), costing a little tightness.

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 lookup with annotations and an output schema, the description covers the two things it must: what content is searched and when to route elsewhere. Only result behavior (how many articles, ranking, whether it returns snippets) is left implicit, and the output schema likely handles that.

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?

With one parameter at 100% schema coverage, the schema already documents the query string, its length bounds, and gives an example. The description's framing ('the question about Zola') corroborates but adds no new syntax or formatting guidance beyond the schema, so the baseline 3 applies.

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 concrete verb+resource (search Zola Help Center articles) and enumerates the covered domains: registry, gift orders and shipping, cash funds and fees, wedding website, invitations, guest list, vendor marketplace, account. It explicitly excludes general wedding advice, which cleanly separates it from zola_search_wedding_advice and other topical siblings.

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

Usage Guidelines5/5

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

Opens with a when-to-use trigger ('the user asks how a Zola product or service works'), then gives negative cases: not general wedding advice, and not the state of the couple's own orders, gifts, cash fund or store credit. It names the four alternative tools to use in those cases (zola_get_my_order_history, zola_get_my_gift_tracker, zola_get_my_cash_fund_status, zola_get_my_credits).

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