BrandKity MCP Server

Official

by BrandKity

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

list_kits

Retrieve all brand kits from your workspace, with optional filtering by draft, published, or all statuses.

Instructions

List all brand kits in the workspace. Optionally filter by status (draft, published, or all).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_kits"
  }
}

Input Schema

Name	Required	Description	Default
`status`	No	Filter kits by status. Default: all

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.4.2May 28, 2026

TDQS

A3.7/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 discloses the operation is a list with optional filtering, but lacks details on pagination, ordering, rate limits, or whether the list is complete or batched.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no wasted words. Front-loaded with the primary action and includes the key optional parameter. Highly efficient.

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 core functionality but omits expected details for a list operation, such as return format, pagination, or sorting. Given no output schema, such information would enhance completeness.

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 description coverage is 100%: the only parameter 'status' is fully described in the schema with an enum and default. The description adds no extra semantic meaning beyond what the schema already provides.

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 lists all brand kits in the workspace, with an optional filter by status. It distinguishes from sibling tools like get_kit (single kit) and create_kit (creation).

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

Usage Guidelines3/5

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

The description implies usage for listing kits but does not explicitly state when to use this versus alternatives (e.g., get_kit for a single kit, or list_blocks for blocks). No exclusion criteria or prerequisites are provided.

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