Skip to main content
Glama
brilliantdirectories

brilliant-directories-mcp

Official
by brilliantdirectories
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

createSmartList

Create a smart list to save filter configurations for later reuse. Supports data sources like members, leads, reviews. Requires name, type, and creator ID with duplicate name check.

Instructions

Create a smart list - Create a new smartlist record. Writes live data.

Use when: programmatically saving a filter configuration for later reuse. smart_list_type determines the data source (members, leads, reviews, etc.).

Required: smart_list_name, smart_list_type, smart_list_created_by.

Pre-check before create: BD does NOT enforce uniqueness on smart_list_name. Duplicate list names mean admins and other tools can't tell the lists apart in the Smart Lists manager, and automations that look up a list by name will bind to the wrong record. Do a server-side filter-find: listSmartLists property=smart_list_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 updateSmartList, OR ask the user, OR pick an alternate smart_list_name and re-check. Never silently create a duplicate.

Parameter interactions:

  • smart_list_type - data source (see Enums)

  • smart_list_created_by - admin user ID creating the list

  • smart_list_query_params - JSON/string of filter criteria specific to the chosen type

  • schedule - recurrence if the list should auto-refresh

See also: updateSmartList (modify existing).

smart_list_query_params format depends on smart_list_type:

  • For smart_list_type=newsletter: store a URL string (admin view uses it directly as an href link - no filter semantics).

  • For ALL other types (members, leads, reviews, transaction, forms_inbox): pass a JSON string of filter key-value pairs, e.g. {"subscription_id":"1","active":"1"}. The backend encrypts it internally before storing.

  • If empty / no filters: pass "NA" (the controller defaults missing values to this).

The API accepts the value as a plain string; BD handles the internal encryption. Don't pre-encrypt client-side - you'll get double-encrypted garbage. Use the JSON-key-value format for filterable types.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
smart_list_nameYes
smart_list_typeYes
smart_list_created_byYesAdmin user ID
smart_list_query_paramsNoFilter criteria — format depends on `smart_list_type`: - **newsletter** - pass a URL string (used directly as `href`) - **all other types** (members, leads, reviews, transaction, forms_inbox) - pass a JSON string of key-value filter pairs like `{"subscription_id":"1","active":"1"}` - **no filters** - pass `"NA"` Backend encrypts internally - do NOT pre-encrypt client-side.
scheduleNoRecurrence frequency

Tool Definition Quality

A4.7/5.0
Behavior5/5

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

Discloses encryption behavior for query_params, warns about duplicate name consequences, and explains parameter interactions. Annotations are minimal but consistent; no 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?

Well-structured with labeled sections and front-loaded purpose. However, the query_params explanation is lengthy; could be more concise while retaining clarity.

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?

Covers purpose, usage, pre-conditions, parameter details, and format dependencies. Lacks description of return value (e.g., created list ID) given no output schema, but is otherwise thorough.

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?

Adds meaning for 'smart_list_name' (no schema description) and 'schedule' (auto-refresh context). Reinforces other params but does not significantly surpass schema descriptions.

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 'Create a new smartlist record' with a specific verb and resource. It differentiates from siblings by mentioning 'updateSmartList' and implying creation is for new configurations.

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 mentions when to use ('programmatically saving a filter configuration for later reuse') and provides a pre-check for duplicates with clear instructions to avoid and alternative reuse via 'updateSmartList'.

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