Skip to main content
Glama
brilliantdirectories

brilliant-directories-mcp

Official

updateFormField

Modify form field properties like text, type, order, or required status in Brilliant Directories to customize data collection and user input.

Instructions

Update a form field

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
field_idYes
field_textNo
field_typeNoForm 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_orderNo
field_requiredNo
Behavior2/5

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

With no annotations, the description carries full burden but only states the action ('Update') without behavioral details. It doesn't disclose required permissions, whether updates are destructive or reversible, rate limits, or what happens to unspecified fields. 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 a single, efficient sentence with zero waste. It's front-loaded and appropriately sized for the tool's purpose, avoiding unnecessary elaboration that could be inferred from the schema.

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?

For a mutation tool with 5 parameters, no annotations, and no output schema, the description is incomplete. It lacks behavioral context (e.g., permissions, side effects), usage guidelines, and details on return values or error handling, leaving significant gaps for an agent to use it 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 doesn't explicitly mention parameters, but the input schema has high detail (e.g., field_type enum with extensive descriptions covering 80%+ of semantic info). Schema description coverage is 20%, but the enum descriptions compensate significantly, providing clear meaning for field_type and implying usage for other params like field_text. Baseline is 3 due to schema doing heavy lifting, but the rich enum context elevates it.

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 'Update a form field' clearly states the verb ('Update') and resource ('form field'), but it's vague about what aspects can be updated. It doesn't distinguish from sibling tools like 'updateForm' or 'createFormField', which handle different operations on related resources.

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 is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing form field), exclusions, or comparisons to siblings like 'createFormField' for new fields or 'updateForm' for form-level changes.

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