Skip to main content
Glama
BrandKity

BrandKity MCP Server

Official
by BrandKity

upload_assets_batch

Upload multiple local files to a single brand kit block in one call. Automatically skips duplicate file paths for bulk asset management.

Instructions

Batch upload multiple local files into a single block with one tool call. Duplicate file_path values in the list are automatically skipped — each unique path is uploaded only once. Use for logos, visuals, videos, collaterals, resources, and icons. For files larger than 50 MB, prefer uploading individually with upload_asset. If the batch partially fails, resubmit only the failed files.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kit_idYesKit UUID
block_idYesBlock UUID
block_typeYesTarget block type (used for MIME validation and storage path)
filesYesList of files to upload in a single batch request (max 100 files)
parallelismNoHow many files to upload concurrently. Default: 3 (max: 6)
continue_on_errorNoIf true, continues uploading after failures and returns a partial result. Default: true
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses duplicate skipping, partial failure retry, and preference for individual uploads for large files. Could mention response format, but otherwise strong.

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?

Four concise, front-loaded sentences. No redundant information. Each sentence adds value: purpose, dedup, use cases, large file guidance, failure handling.

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?

Lacks return value description and error handling details beyond partial failure. No output schema, so description should hint at response. Otherwise covers key aspects.

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 descriptions cover all 6 parameters with 100% coverage. Description adds minimal extra meaning beyond what schema already provides (e.g., block_type explanation).

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 batches multiple local files into a single block and lists specific use cases (logos, visuals, videos, etc.). It distinguishes from sibling tool upload_asset by mentioning large file handling.

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: use upload_asset for files larger than 50 MB, resubmit failed files on partial failure. Also explains automatic duplicate skipping.

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