Skip to main content
Glama

import_brand_kit_modules

Import structured brand data including research, profile, voice, competitors, ICPs, journey, USPs, messaging, content pillars, and guidelines into a brand kit.

Instructions

Import brand kit modules

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
icpsNoIdeal Customer Profiles with demographics, goals, pain points, and jobs-to-be-done.
uspsNoUnique Selling Propositions with proof points and ICP mapping. References ICPs by profile_name for M2M linking.
brand_idYesBrand kit UUID
brand_voiceNoVoice characteristics, tone spectrum, vocabulary guidelines, and example copy pieces.
brand_profileNoBrand identity including mission, vision, personality archetype, core values, and positioning statement.
content_pillarsNoContent pillars with allocation percentages, sample topics, ICP matrix, and journey stage mapping.
brand_guidelinesNoConsolidated brand guidelines document covering all brand elements, stored as a KnowledgeBase entry.
company_researchNoCompany research data including products, brand assets, digital presence, and market context.
customer_journeyNoMulti-stage customer journeys with touchpoints, content needs, and conversion factors.
market_positioningNoMarket category, positioning map, white space opportunities, and market trends.
competitor_analysisNoCompetitor profiles with threat levels, strengths, weaknesses, and competitive positioning.
messaging_frameworkNoElevator pitches, ICP-specific messages, objection handlers, taglines, and social bios.
Behavior2/5

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

No annotations provided. The description does not disclose whether the import is additive or overwrites existing modules, what side effects occur, or any authorization needs. Minimal behavioral insight.

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

Conciseness2/5

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

The description is extremely brief (3 words), which is concise but at the cost of clarity. It underspecifies the tool's function and lacks any structured detail.

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

Completeness1/5

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

With 12 parameters, no output schema, and no annotations, the description provides almost no context. It fails to explain what 'importing' means, what the return value is, or error handling.

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 the description doesn't need to add parameter details. However, it adds no extra meaning about parameter relationships or usage patterns. Baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Import brand kit modules' gives a verb and resource, but doesn't clearly distinguish from sibling tools like 'build_brand_kit' or 'create_brand_kit'. It implies adding modules to an existing brand kit (via brand_id required), but this is not explicit.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. The description lacks any context about prerequisites, typical scenarios, or when not to use it.

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

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