Skip to main content
Glama
brilliantdirectories

brilliant-directories-mcp

Official

createFormField

Add form fields to Brilliant Directories forms for collecting user data, including text inputs, dropdowns, checkboxes, file uploads, and specialized fields like email validation or rich text editors.

Instructions

Create a form field

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
form_nameYesParent form slug
field_nameYesDB column name
field_textYesDisplay label
field_typeYesForm field type. Authoritative list from BD admin form-field editor, grouped by category:\n\nSELECT FIELDS (user picks from options):\n Checkbox = Checkboxes (multi-select)\n Select = Dropdown list (single-select)\n Radio = Multiple choice radios (single-select)\n YesNo = Yes or No toggle\n\nTEXT INPUTS:\n Custom = Custom HTML injection\n Email = Email address input (validates format)\n HTML = Section title / HTML heading (display-only)\n Button = Submit form button\n Textbox = Single-line text input\n textarea = Multi-line textarea (note: lowercase)\n Url = Website URL input\n\nFANCY FIELDS:\n Date = Calendar date picker\n DateTimeLocal = Calendar date+time picker\n File = File upload\n FroalaEditor = Froala rich text editor (basic)\n FroalaEditorUserUpload = Froala + user image upload\n FroalaEditorUserUploadPreMadeElem = Froala + upload + pre-made elements\n FroalaEditorAdmin = Froala with admin media manager access\n Tip = Help alert box (display-only)\n Hidden = Hidden field (not rendered, stores value)\n Country = Country dropdown\n State = State dropdown\n Number = Integer-only number input\n Password = Password field (masked)\n Phone = Phone number input\n CountryCodePhone = Phone input with country code\n Pricebox = Price input\n ReCaptcha = Google reCAPTCHA security\n HoneyPot = Hidden honeypot (anti-spam)\n Category = Top-level category list\n Years = Year picker\n\nNote on casing: most values are TitleCase but "textarea" is lowercase — copy exact spelling from the enum. For most simple text collection use Textbox; for paragraphs use textarea; for emails use Email so BD validates the format.\n\nFor Checkbox / Select / Radio types, you must also supply the options list via the field_options parameter (if exposed).
field_orderYes
field_requiredNo
field_placeholderNo
field_input_viewNoShow in edit form
field_display_viewNoShow in public view
field_email_viewNoInclude in notifications
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Create a form field' implies a write/mutation operation, but it fails to describe critical behaviors: required permissions, whether the creation is idempotent or reversible, error conditions, or what happens on success (e.g., returns a field ID). This is inadequate for a mutation tool with zero annotation coverage.

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?

The description is extremely concise with a single sentence, 'Create a form field', which is front-loaded and wastes no words. While this brevity leads to underspecification in other dimensions, it meets the criteria for conciseness by avoiding redundancy or unnecessary elaboration.

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

Completeness2/5

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

Given the complexity (10 parameters, mutation tool, no annotations, no output schema), the description is severely incomplete. It does not explain the tool's role in the broader context (e.g., relation to forms), behavioral expectations, or usage scenarios. This leaves significant gaps for an agent to understand and invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds no parameter semantics beyond the input schema, which has 70% coverage (7 of 10 parameters described). However, with 10 parameters and no output schema, the baseline is high. The schema's detailed enum descriptions for 'field_type' compensate well, but the description itself contributes nothing additional, keeping it from a perfect score.

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

Purpose2/5

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

The description 'Create a form field' is a tautology that merely restates the tool name without elaboration. It specifies the verb ('Create') and resource ('a form field'), but lacks any detail about what this entails or how it differs from sibling tools like 'createForm' or 'updateFormField'. This provides minimal value beyond the name itself.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus alternatives. The description does not mention prerequisites (e.g., needing an existing form), exclusions, or comparisons with sibling tools such as 'createForm' (for creating the parent form) or 'updateFormField' (for modifying existing fields). This leaves the agent without context for appropriate tool selection.

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