Skip to main content
Glama
brilliantdirectories

brilliant-directories-mcp

Official

getUser

Read-onlyIdempotent

Retrieve a single member record by user ID, with optional inclusion of fields such as subscription, photos, transactions, and other details.

Instructions

Get a single member/user - Fetch a single user record. Read-only.

Lean-by-default keep-list: same shape as listUsers — identity + routing + location core (user_id, first_name, last_name, email, company, phone_number, subscription_id, profession_id, active, status, city, state_code, country_code, filename, image_main_file, signup_date, last_login, modtime). Restore extras via flags: include_password=1, include_subscription=1, include_clicks=1, include_photos=1, include_transactions=1, include_profession=1, include_tags=1, include_services=1, include_seo_hidden=1, include_about=1, include_legacy_fields=1, include_extras=1 (billing/analytics rollups revenue/card_info/total_clicks/total_photos, duplicate location fields state_ln/country_ln/full_name/user_location/zip_code/lat/lon, plus social URLs, awards, credentials, position, quote, work_experience, ref_code, booking_link, etc.).

Use when: you already have the user_id (from listUsers, searchUsers, a prior create, or a webhook payload) and need the full member record. Cheaper than listUsers + filter. For lookups by email or other field, use listUsers with property/property_value.

Required: user_id.

See also: listUsers (enumerate many), searchUsers (keyword search).

Returns: { status: "success", message: [{...record}] } - the message array contains 1 lean-shaped record when found. Empty or HTTP 404 when not found.

Payment method on file (under include_extras=1): card_info is false when no card is stored (BD convention), or an object with last4/brand/name when one is. Use card_info && card_info.last4 to safely check. Authoritative signal for "does this member have a payment method" — don't infer from subscription_id alone.

Profile URL: every user record has a filename field. To get the full public profile URL, concatenate: <site-domain>/<user.filename>. The filename is the complete relative path (e.g., united-states/monterey-park/doctor/harrison-hasanuddin-d-o) - DO NOT prepend /business/, /profile/, /member/, or any other segment. BD's router resolves filename verbatim. Note: filename is regenerated by BD when member inputs that influence the slug change (category, city, etc.). The value you see NOW is current-as-of-this-read. If you call updateUser afterward, re-fetch before using the filename in URL-referencing content (blog posts, emails, redirects).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYes
include_passwordNoOpt in to return bcrypt `password` hash. Default stripped.
include_subscriptionNoOpt in to return full `subscription_schema` (60+ plan fields). Default: `subscription_id` only.
include_clicksNoOpt in to return `user_clicks_schema.clicks` array. Default: `total_clicks` count surfaced only when > 0; absent means zero clicks.
include_photosNoOpt in to return `photos_schema` array. Default: `total_photos` count only (`image_main_file` URL always returned).
include_transactionsNoOpt in to return full `transactions` invoice array. Default stripped (`revenue` rollup always returned).
include_professionNoOpt in to return `profession_schema` (category metadata). Default: `profession_id` only.
include_tagsNoOpt in to return `tags` array. Default stripped.
include_servicesNoOpt in to return `services_schema` sub-category array. Default stripped.
include_seo_hiddenNoOpt in to return SEO meta fields (`seo_page_*_hidden`, `seo_social_*_hidden`, `search_description`). Default stripped.
include_aboutNoOpt in to return the `about_me` HTML bio. Default stripped.
include_legacy_fieldsNoReturn image-import state on `photos_schema` rows: `original`, `resized`, `error`. Requires `include_photos=1`.
include_extrasNoOpt in to return ALL remaining fields on this resource that are not in the lean-by-default keep-list and not gated by another `include_*` flag. Lean default returns only the core identity, routing, and load-bearing fields. `include_extras=1` restores everything else (geo, all hero_*, layout/sidebar/menu config, all display toggles, admin metadata, etc.). Resource-specific — see each tool's description for what the extras bundle contains.
Behavior5/5

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint, openWorldHint. The description adds substantial context beyond annotations, including the lean-by-default keep-list, behavior of include flags, return format, filename regeneration, and payment method detection logic. No contradictions.

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 bold headings, bullet points, and clear sections (purpose, usage, params, return, notes). While lengthy, every sentence serves a purpose. Some redundancy (e.g., 'Get a single member/user' repeated) could be trimmed, but overall structure is effective.

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?

For a tool with 13 parameters and no output schema, the description is extremely thorough: covers return format, success/error behavior (empty array/404), special fields (card_info), filename usage and regeneration caveat, and references to siblings. It leaves no important aspect unaddressed.

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 high (92%), so baseline 3. The description adds significant value by explaining the lean-by-default keep-list, the purpose of each include flag (e.g., 'include_extras' bundle content), and the semantics of 'card_info'. However, the schema already documents most parameters, so the description supplements rather than replaces.

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 explicitly states 'Get a single member/user - Fetch a single user record', clearly identifying the tool's action and target. It differentiates from siblings like listUsers (enumerate many) and searchUsers (keyword search), providing clear purpose.

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 provides explicit when-to-use guidance: 'Use when: you already have the user_id...' and contrasts with alternatives: 'For lookups by email or other field, use listUsers with property/property_value.' It also includes a caveat about re-fetching filename after updateUser.

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