Skip to main content
Glama
brilliantdirectories

brilliant-directories-mcp

Official

listCities

Read-onlyIdempotent

List cities from the directory site to retrieve city slugs for constructing SEO-friendly search-result URLs and location-based member browsing. Supports pagination and filtering by city name, state, or country.

Instructions

List cities (location-based search & SEO slugs) - Paginated enumeration of cities enabled on this site for location-based member/post browsing and SEO page URL generation. Read-only source-of-truth for city slugs used in search-result URLs. Backed by BD's location_cities table.

Use when: resolving a human city name (e.g. "Beverly Hills") to its city_filename slug (e.g. beverly-hills) before constructing a search-result URL for a static SEO page, or discovering which cities this site has seeded.

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. Useful filters: city_ln (full name, exact match), city_filename (slug, exact), state_sn (scope to one state), country_sn (scope to one country).

Returns: { status: "success", message: [...rows] } - each row has:

  • locaiton_id (integer PK, BD schema typo - it is locaiton_id, NOT location_id; pass the typo'd form when looking up a single record)

  • city_ln (full name)

  • city_filename (URL slug)

  • state_sn (2-letter state/province code; references location_states.state_sn)

  • country_sn (2-letter country code; references list_countries.country_code)

System-critical table - create & delete deliberately omitted from this MCP. Cities are managed by BD automatically (a new city row is added when a member signs up from a new location). Creating cities via API risks slug collisions with auto-created rows, and deleting risks orphaning members whose city references the row. Use updateCity only for corrections (rename, fix typo in filename). For new cities, let the next member signup seed it.

Auth: X-Api-Key header. Rate limit: 100 req/60s (on 429, back off 60s). Errors: { "status": "error", "message": "..." } - empty-result responses return {status: "error", message: "location_cities not found", total: 0} (same ambiguous pattern as other list endpoints).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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
Behavior5/5

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

Describes pagination semantics, filter/sort behavior, return format including a known typo in the schema (locaiton_id), and error handling patterns. Also discloses auth and rate limits. No contradiction with 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 sections for use cases, pagination, filters, return format, and limitations. Front-loaded with purpose, though somewhat lengthy; each section serves a distinct purpose.

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's complexity (7 params, pagination, filters, critical table, no output schema), the description fully covers return format, common use cases, and constraints, making it self-sufficient for correct invocation.

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?

While input schema has 100% coverage, description adds value by explaining how filter parameters map to specific fields (city_ln, city_filename) and pagination with cursor/page, enhancing clarity beyond the schema.

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 it lists cities for location-based search and SEO slugs, distinguishing it from sibling list endpoints like listCountries and listStates. It specifies the resource and verb with precise context.

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 when to use (resolving city names to slugs, discovering seeded cities) and when not to (no create/delete, risks slug collisions). Provides clear guidance on alternatives like updateCity and avoiding API creation.

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