Skip to main content
Glama
brilliantdirectories

brilliant-directories-mcp

Official

createDataType

Define a new content-type template for your directory. Verify unique category name to prevent admin UI corruption and ensure proper post organization.

Instructions

Create a data type - Define a new content-type template. Only do this when the user explicitly wants a new post type - most sites come pre-configured with the types they need.

Use when: adding a new data-type classifier. Rare - usually preconfigured.

Required: category_name, category_active.

Pre-check before create: BD does NOT enforce uniqueness on category_name or the derived system_name. Duplicate data types corrupt the post-type admin UI, break post-listing widgets that bind by name, and risk posts landing under the wrong type. Do a server-side filter-find: listDataTypes property=category_name property_value=<proposed> property_operator==. Zero rows = name free; >=1 row = taken. Do NOT paginate unfiltered lists - filtered lookup is one tiny response. If taken: reuse via updateDataType, OR ask the user, OR pick an alternate category_name and re-check. Never silently create a duplicate.

Enums: category_active: 1=active and available for members to use, 0=inactive; limit_available: 0, 1.

See also: updateDataType (modify existing).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
category_nameYesDisplay name for this content type (e.g. "Single Photo Post", "Multi-Photo Post", "Video Post")
category_activeYes1 = active and available for members to use; 0 = inactive
limit_availableNo1 = membership-plan posting limits apply to this data type; 0 = no per-plan limits
Behavior4/5

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

Annotations are minimal (readOnlyHint=false, destructiveHint=false). The description adds crucial behavioral context: system does not enforce uniqueness, duplicates corrupt UI, and advises a pre-check. Does not cover other behaviors like auth or rate limits, but adequately addresses the main risk.

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?

Well-structured with clear sections (Use when, Required, Pre-check, Enums, See also). Front-loaded with purpose, but the pre-check block is somewhat lengthy. However, it remains organized and easy to follow.

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?

Given 3 parameters with 100% schema coverage and no output schema, the description covers pre-conditions, duplicate prevention, and alternative actions. It provides sufficient context for an AI agent to use the tool correctly.

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%, baseline 3. The description repeats some enum values and provides minimal additional context beyond the schema descriptions, e.g., stating that category_active indicates availability for members.

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 creates a new data-type template, distinguishes itself from updateDataType, and notes that it's rarely needed as sites come pre-configured.

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?

Explicitly states when to use (user explicitly wants new post type) and when not to (most pre-configured). Provides pre-check steps and alternatives like updateDataType if duplicate exists.

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/brilliantdirectories/brilliant-directories-mcp'

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