Skip to main content
Glama
Sign In
BrandKity MCP Server

BrandKity MCP Server

Official
by BrandKity
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_files

Browse files stored in your workspace. Filter by type to find specific assets like fonts, images, or documents, and retrieve public URLs for each file.

Instructions

List files in your workspace storage. Filter by type to find fonts, images, documents, etc. Returns public URLs for each file.

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_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoFilter by file type. Use 'font' to find previously uploaded font files.all
pageNoPage number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.2

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description must disclose behavior. It states 'Returns public URLs for each file', indicating read-only behavior. However, it lacks details on pagination, ordering, or potential empty results.

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 concise sentences front-load the purpose and add filtering and return info. No redundant or unnecessary content.

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

Completeness4/5

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

For a simple list tool with two parameters and no output schema, the description covers core functionality and return value. Minor gap: paging behavior (e.g., page parameter default) is not explained.

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 adds marginal value. It reinforces the type parameter's filtering purpose but does not add significant new meaning 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 verb 'List' and the resource 'files in your workspace storage'. It distinguishes from sibling tools like upload_file or list_blocks by focusing on listing stored files.

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 provides context by suggesting filtering for fonts, images, documents, etc., but does not explicitly state when to use this tool versus alternatives 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.

Deploy Server

Other Tools