Skip to main content
Glama
brilliantdirectories

brilliant-directories-mcp

Official

getBrandKit

Read-onlyIdempotent

Retrieve the site's brand colors and fonts to maintain visual consistency across all design outputs. Call once at the start of any design task.

Instructions

Get the site's brand kit (colors + fonts) for design decisions - Return a compact, semantically-labeled brand kit for this BD site - colors (body / primary / dark / muted / success / warm / alert accents, card surface) + fonts (body + heading Google Fonts). Call this ONCE at the start of any design-related task (building a widget, WebPage, post template, email, hero banner - anything where colors or fonts are chosen) so the output visually matches the site's brand.

Handler is synthetic - makes 20 parallel internal calls to /api/v2/website_design_settings/get?property=setting_name&property_value=custom_N&property_operator== (one per brand-kit slot), then transforms the raw custom_N values into semantic labels. Uses BD's canonical mapping (same mapping BD's admin AI Companion applies). Parallel calls complete in ~1s wall-clock on typical sites; well under the 100 req/60s rate limit even on repeated invocations.

No args. Read-only. Safe to call anytime.

Response shape:

{
  body: { background, text, font },
  primary: { color, text_on },
  dark: { color, text_on },
  muted: { color, text_on },
  success_accent: { color, text_on },
  warm_accent: { color, text_on },
  alert_accent: { color, text_on },
  card: { background, border, text, title },
  heading_font: "<google font family>",
  usage_guidance: { primary, dark, muted, success_accent, warm_accent, alert_accent, tint_rule, font_rule }
}

Usage guidance embedded in response - agents should read it every call. Key rules:

  • Primary = brand color - main CTAs, dominant accents.

  • Dark = high-contrast sections or strong backgrounds.

  • Muted = subtle section backgrounds, dividers, badges, pills.

  • Success / Warm / Alert accents = specific semantic states (confirmations / attention / urgency). Use sparingly.

  • Tint rule: derive lighter/darker tints from palette colors for hover states, gradients, low-emphasis backgrounds. Do NOT introduce new unrelated hues.

  • Font rule: the site's body.font and heading_font Google Fonts are already globally loaded by BD. Do NOT redefine them in content_css. To switch to a different font, load it via a <link rel="stylesheet" href="https://fonts.googleapis.com/..."> tag in content_head — never @import inside CSS (Outlook + some BD widget contexts strip or fail on @import).

When a slot is empty on the site, the handler applies BD's documented fallback defaults (same defaults BD's admin AI Companion uses). Response is never missing keys - every field always has a value.

Auth: X-Api-Key header. Rate limit: 100 req/60s. Caches well on the agent side - the brand kit rarely changes within a session; call once, reuse.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. Description adds valuable behavioral details: 20 parallel internal calls, rate limit, caching advice, fallback defaults, and response shape with usage guidance. No contradictions.

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?

Description is lengthy but well-structured, front-loading purpose and usage. Every sentence adds value, though some technical details could be condensed. Still earns a 4 for being informative without redundancy.

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?

Despite no output schema, description provides comprehensive detail on response shape, usage guidance, and edge cases (empty slots, auth, rate limit). Fully equips the agent to use the tool correctly.

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?

No parameters exist (0 params, schema coverage 100%), so baseline score is 4. Description mentions 'No args.' which is sufficient; no further parameter info needed.

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?

Description clearly states the tool retrieves the site's brand kit (colors and fonts) for design decisions. It specifies use cases like building widgets, webpages, etc., and distinguishes itself from siblings by its unique purpose.

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?

Explicitly instructs to call 'ONCE at the start of any design-related task' and notes 'Safe to call anytime.' Provides clear context for when to use the tool, leaving no ambiguity.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/brilliantdirectories/brilliant-directories-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server