Skip to main content
Glama
BrandKity

BrandKity MCP Server

Official
by BrandKity

add_block

Creates a new brand block unconditionally. Use only after confirming no block of the same type exists in the kit.

Instructions

IMPORTANT: prefer ensure_block over this tool — ensure_block is idempotent and prevents duplicates. add_block creates a new block unconditionally. Calling it twice creates two separate blocks of the same type. Only use add_block when you have already confirmed via list_blocks that no block of this type exists. Block types: • colors — brand palette swatches (use add_colors) • typography — font entries (use add_typography) • rich_text — brand story / guidelines text (use set_brand_story) • logos — logo variants uploaded as SVG/PNG (use upload_asset with block_type=logos) • visuals — brand photography / illustrations (use upload_asset with block_type=visuals) • videos — brand video assets (use upload_asset with block_type=videos) • icons — SVG icon library (use upload_asset with block_type=icons) • collaterals — downloadable files like PDFs (use upload_asset with block_type=collaterals) • resources — source files, Figma, ZIPs (use upload_asset with block_type=resources)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kit_idYesKit UUID
typeYesBlock type
nameNoCustom display name for the block. Defaults to the type label.
Behavior4/5

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

With no annotations, the description carries the full burden. It warns that calling twice creates duplicates and advises using ensure_block for idempotency. However, it does not disclose permissions, side effects, or error behavior. The duplicate warning is a key behavioral trait.

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 long but well-structured, starting with a warning and then providing clear usage guidance and a mapping of block types to alternative tools. Every sentence adds value, though it could be slightly more concise.

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 lacks information about the return value or output of the tool, and does not mention error handling or permissions. Given that there is no output schema, this is a gap. However, it covers the usage context well.

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?

Schema coverage is 100%, so baseline is 3. The description does not add meaning beyond what the schema provides. The list of block types and their preferred tools is useful but relates to usage guidelines rather than parameter semantics.

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 that the tool creates a new block unconditionally and distinguishes it from ensure_block and other sibling tools for specific block types. The verb 'creates' and resource 'block' are specific and unambiguous.

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?

Explicit guidance is provided: prefer ensure_block, only use add_block after confirming via list_blocks, and each block type has a recommended tool. This clearly tells when and when not to use the tool.

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/BrandKity/mcp-server'

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