Skip to main content
Glama
brilliantdirectories

brilliant-directories-mcp

Official

listFormFields

Read-onlyIdempotent

Enumerate form fields with cursor-based pagination and filters. Retrieve field metadata like JSON meta for validators or view flags for editing.

Instructions

List form fields - Paginated enumeration of formfield records. Read-only.

Use when: listing fields on a form. Filter by form_name (text slug — form_fields joins to forms by form_name, not form_id).

Pagination: cursor-based (limit, page). See Rule: Pagination for full cursor/cap/stop semantics.

Filter/sort: property+property_value+property_operator, order_column+order_type. See Rule: Filter operators for the verified-working operator set, silent-drop detection, and derived-field unfilterability.

See also: getFormField (single record by ID).

Returns: { status: "success", total, current_page, total_pages, next_page, prev_page, message: [...records] }. Each record is the full resource object.

Site records and platform master defaults are merged in the response — see Rule: Default-merge models to filter to one and to sort.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPagination cursor (use next_page from previous response)
limitNoRecords per page (default 25, max 100)
propertyNoColumn key to filter by (present on the response rows; a wrong name silently returns empty). For multi-condition AND, pass parallel arrays here and in `property_value`/`property_operator` — equal length, Nth entries paired. See Rule: Compound filters.
order_typeNoSort direction: ASC or DESC
include_metaNoOpt in to return the `json_meta` longtext blob (UI rendering metadata + per-field validator config). Default stripped — use when adding or editing per-field validators (regexp, stringLength, etc.). See **Rule: Forms** § Field anatomy → `json_meta`.
order_columnNoColumn to sort by — a column key present on the response rows (a wrong name silently returns empty)
property_valueNoValue to filter by; array to pair with a `property` array (same length).
property_operatorNoFilter operator (word-form; symbol forms WAF-stripped). Single: eq, ne, lt, lte, gt, gte, like, not_like. CSV: in, not_in, between. Substring: contains, starts_with, ends_with (+not_). Date: year_eq, month_eq, day_eq (+not_), since_days, until_days. Length: length_eq, length_lt, length_gt, length_between. Null: is_set, is_not_set, is_null, is_not_null. Array to pair with a `property` array (same length). See Rule: Filter operators for value shapes.
include_view_flagsNoOpt in to return form-field view-flag columns: `field_input_view`, `field_display_view`, `field_search_view`, `field_email_view`, `field_grid_view`, `field_input_view_admin_only`, plus the 5 alt-label override columns. Default stripped — use when actively editing field visibility. See **Rule: Forms** § Field anatomy.
Behavior5/5

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

The description explicitly labels the tool as 'Read-only' and describes pagination ('cursor-based'), return structure, and merging behavior with site records and platform defaults. It references rules for filter operators and pagination semantics. This adds significant behavioral context beyond the annotations (readOnlyHint, openWorldHint, idempotentHint) without contradiction.

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?

The description is well-structured with clear sections: 'Use when:', 'Pagination:', 'Filter/sort:', 'See also:', 'Returns:'. It is front-loaded with purpose. While slightly lengthy, it is concise given the complexity of the 9 parameters and the need to cover filtering, pagination, and default merging.

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

Completeness5/5

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

With no output schema, the description provides a detailed return structure and explains that records include merged defaults. It covers all 9 parameters with additional context and references rules for detailed filter operators and pagination. This gives a comprehensive understanding of the tool's behavior.

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?

Schema coverage is 100%, so baseline is 3. The description adds extra meaning for parameters like property (explains multi-condition AND with parallel arrays), include_meta (use case for editing validators), and include_view_flags (visibility flags). It also references external rules for filters and forms, providing more context than schema alone.

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 'List form fields - Paginated enumeration of formfield records. Read-only.' The verb 'list' and resource 'form fields' are specific. It distinguishes from siblings like getFormField (single record) by explicitly mentioning it in 'See also: getFormField'.

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?

The description states 'Use when: listing fields on a form.' and provides specific filtering guidance (filter by form_name, joins by text slug not ID). It also mentions 'See also: getFormField' as an alternative for single records, helping the agent decide.

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