Skip to main content
The glossary is where you define the terms your team should always use and the terms it should avoid. It works alongside your brand voice to enforce terminology at the point of content generation. When an AI tool connected through the MCP server creates content, it checks your glossary and applies the correct terms automatically. You can think of the glossary as two lists. Preferred terms are the approved names, acronyms and phrases your organization has standardized on. Avoid terms are words and phrases your team should not use, each paired with a recommended alternative. Together, these lists eliminate inconsistency before it reaches your audience.

​
How it works

When you add a term to the glossary, it becomes a constraint that AI tools enforce during content generation. Preferred terms are always used exactly as written. Avoid terms are automatically replaced with the alternatives you specify. The glossary is workspace-wide. Every member of your workspace shares the same terminology, and any connected AI tool has access to it through the MCP server. Changes take effect the next time content is generated.

​
Two term types

The glossary supports two types of entries, each with different behavior and configuration options. Preferred terms define the correct way to reference a product, feature, concept or acronym. You can mark a preferred term as a proper noun, assign a short name for abbreviation handling and list related names that should not be used. For a full breakdown of preferred term fields and behavior, see Preferred terms. Avoid terms define language your team should not use. Each avoid term includes one or more recommended alternatives. When AI tools encounter a reason to use an avoided term, they substitute one of the alternatives instead. For details on how avoid terms work, see Avoid terms.

​
Adding a term

In your Brivvy workspace, navigate to the glossary. Select the type of term you want to add: preferred or avoid. Fill in the required fields and save. The term is immediately available to all connected AI tools.

​
Best practices

  • Keep entries concise. A glossary works best when each entry is specific and unambiguous.
  • Review your glossary quarterly. Terminology changes as your product evolves, and outdated entries create confusion.
  • Coordinate with your voice configuration. The glossary handles terminology while voice handles tone and style. Use both together for full coverage.
  • Start with your most common pain points. If your team frequently misspells a product name or uses an outdated term, add those first.
  • Preferred terms to learn how to configure terms your team should always use.
  • Avoid terms to learn how to flag language your team should not use.
  • Voices to configure the tone and rules that work alongside your glossary.
  • MCP Server to connect AI tools that enforce your glossary during content generation.