BrandKity MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

add_typography

Add font entries to a typography block using Google Fonts, Adobe Fonts, custom uploads, or system fonts. Specify font family, weights, and usage role.

Instructions

Add font entries to a Typography block. Four sources are supported: (1) "Google Fonts" — provide font_family, weights, usage. Fully automated. (2) "Adobe Fonts" — provide font_family + asset_url (Typekit CSS URL from fonts.adobe.com → Web Projects → Get embed code). (3) "Custom" — first upload the font file using upload_file tool, then pass asset_url (the returned URL) here. (4) "System" — provide font_family only (font must be available on the OS).

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": {
      "kit_id": "<kit_id>",
      "block_id": "<block_id>",
      "fonts": "<fonts>"
    },
    "name": "add_typography"
  }
}

Input Schema

Name	Required	Description
`kit_id`	Yes	Kit UUID
`block_id`	Yes	Block UUID (must be a typography block)
`fonts`	Yes	Array of font entries to add (max 20)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.4.2May 28, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It explains the behavior for each source (e.g., Google Fonts is 'Fully automated', Adobe Fonts requires asset_url). However, it does not disclose potential errors, rate limits, or the outcome of adding fonts (e.g., whether it overwrites existing entries).

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?

The description is a single paragraph with clear enumeration of sources. It is well-structured and efficiently conveys necessary information, though it could be slightly more concise without losing value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the tool's purpose and usage well, but lacks information about return values or error handling. Since no output schema exists, this gap is notable. It is adequate for a tool with three required parameters but not fully complete.

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 baseline is 3. The description adds value by explaining the usage of asset_url for Custom and Adobe Fonts, and noting that weights default to [400]. This context goes beyond the schema descriptions.

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?

The description clearly states the tool's purpose: 'Add font entries to a Typography block.' It distinguishes itself from siblings by being specific to typography blocks and enumerates four distinct font sources, providing clear differentiation.

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

Usage Guidelines4/5

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

The description provides explicit usage guidance for each source, including prerequisites (e.g., needing to use upload_file tool for Custom fonts). However, it does not explicitly state when not to use the tool or suggest alternative tools, leaving some gap in decision-making.

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