Skip to main content
Glama
brilliantdirectories

brilliant-directories-mcp

Official

listFormFields

Read-onlyIdempotent

Enumerate form fields with pagination, filtering by form name, property, and operator. Supports cursor-based pagination.

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
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`.
limitNoRecords per page (default 25, max 100)
pageNoPagination cursor (use next_page from previous response)
propertyNoField name to filter by
property_valueNoValue to filter by
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. See Rule: Filter operators for value shapes.
order_columnNoColumn to sort by
order_typeNoSort direction: ASC or DESC
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds context: it describes the return format, pagination cursor semantics, and behavioral notes like 'silent-drop detection and derived-field unfilterability.' This adds value beyond the annotations.

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: title, usage, pagination, filter/sort, see also, returns. Uses bold for key terms. While slightly wordy, the structure aids readability. Every sentence adds value, referencing rules without being redundant.

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?

Given the tool has 9 parameters and no output schema, the description is comprehensive. It covers purpose, usage context, pagination, filtering/sorting, sibling tool, and even the return structure. An AI agent can invoke this tool correctly based on the description alone.

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?

Input schema coverage is 100% with detailed parameter descriptions. The description adds overall context such as the form_name join logic and refers to rules for filter operators and pagination. It provides meaning beyond the schema by explaining how parameters interact (e.g., property_operator with property_value).

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 starts with 'List form fields - Paginated enumeration of formfield records. Read-only,' clearly stating the verb and resource. It distinguishes itself from the sibling tool getFormField by noting it's for listing multiple records versus a single record by ID.

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 'Use when: listing fields on a form.' It provides filtering guidance ('Filter by form_name'), pagination rules, and an alternative tool ('See also: getFormField (single record by ID)'). The description also references specific rules for filter operators and pagination.

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