Skip to main content
Glama
brilliantdirectories

brilliant-directories-mcp

Official

updateUser

Modify existing member profiles in Brilliant Directories by updating user fields, managing tags, adjusting credits, handling images, and configuring services.

Instructions

Update an existing member/user — Update any user field. Supports special actions: member_tag_action + member_tags, credit_action + credit_amount, images_action, services, auto_geocode.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYes
emailNo
first_nameNo
last_nameNo
companyNo
phone_numberNo
cityNo
state_codeNo
country_codeNo
subscription_idNo
member_tag_actionNoSet to 1 to modify tags
member_tagsNoComma-separated tag IDs
credit_actionNo
credit_amountNo
images_actionNo
servicesNoFormat: category=>service1,service2
auto_geocodeNoUse Google Maps to geocode this user's location. Requires the "Pretty URLs with Google Maps" feature to be enabled on the site. (string, "1" or "0").\n 1 = Yes\n 0 = No
activeNoThe status of the user after the account is created.\n\nValid values:\n 1 = Not Active - Account Still Requires Activation\n 2 = Active - Account is Live\n 3 = Canceled - Sets User as Canceled Status\n 4 = On Hold - Account Requires Moderation\n 5 = Past Due - Sets User as Past Due Status
listing_typeNoSelect if the newly created user should be marked as an individual person or a company.\n\nValid values:\n Individual = Individual Person\n Company = Company / Organization
verifiedNoIf YES, a verified icon badge will display on the user's listing.\n\nValid values:\n 1 = Yes\n 0 = No
signup_dateNoOPTIONAL: Defines the join date of this user in your database. Leave blank to use the date the user is created. First use Zapier Formatter to customize date "TO FORMAT" to be YYYYMMDDHHmmss.
profession_idNoAssign this user to a top level category. Input the ID number of the top level category.
address1NoThe user's street address.
address2NoThe user's unit or suite number.
zip_codeNoThe user's zip / postal code.
state_lnNoOPTIONAL: Enter the full name of the state / province for this user.
country_lnNoOPTIONAL: Enter the full name of the country for this user.
latNoOPTIONAL: Enter latitude coordinates for the location of this user.
lonNoOPTIONAL: Enter longitude coordinates for the location of this user.
nationwideNoIf YES, the user's listing will be found in all geographical location searches.\n\nValid values:\n 1 = Yes\n 0 = No
search_descriptionNoThe short description about this user. Displays under your user's name on search result pages. 170 Character Limit.
about_meNoThe long description about this user.
quoteNoOPTIONAL: Enter the user's personal quote, motto or slogan.
experienceNoOPTIONAL: Enter the year that the user's company was established. Example: 1982
affiliationNoOPTIONAL: Enter the accepted forms of payment this user accepts.
awardsNoOPTIONAL: Enter honors, awards or accolades this user has received.
rep_mattersNoOPTIONAL: Enter the hours of operation for the member. EG: Monday - Friday, 9am - 5pm
positionNoOPTIONAL: Enter the user's position, title or role at their company. Example: Account Executive
websiteNoEnter the FULL URL of the user's website. Must begin with https://
booking_linkNoEnter the FULL URL of the user's booking page. Must begin with https://
blogNoEnter the FULL URL of the user's blog. Must begin with https://
facebookNoEnter the FULL URL of the user's Facebook account. Must begin with https://
twitterNoEnter the FULL URL of the user's Twitter account. Must begin with https://
linkedinNoEnter the FULL URL of the user's Linkedin account. Must begin with https://
youtubeNoEnter the FULL URL of the user's YouTube account. Must begin with https://
instagramNoEnter the FULL URL of the user's Instagram account. Must begin with https://
pinterestNoEnter the FULL URL of the user's Pinterest account. Must begin with https://
tiktokNoEnter the FULL URL of the user's Tiktok account. Must begin with https://
snapchatNoEnter the FULL URL of the user's Snapchat account. Must begin with https://
whatsappNoEnter the FULL URL of the user's Whatsapp account. Must begin with https://
profile_photoNoOPTIONAL: Enter the FULL URL of the image filename for the user's profile photo. Image URL must already exists somewhere online in order for this field to work properly. URL should begin with http://
logoNoOPTIONAL: Enter the FULL URL of the image filename for the user's profile logo. Image URL must already exists somewhere online in order for this field to work properly. URL should begin with http://
cover_photoNoOPTIONAL: Enter the FULL URL of the image filename for the user's cover photo. Image URL must already exists somewhere online in order for this field to work properly. URL should begin with http://
auto_image_importNoIf YES, system will import user images and save them to your website. Processing may take several minutes after import.\n\nValid values:\n 1 = Yes\n 0 = No
Behavior2/5

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

With no annotations provided, the description carries the full burden. It mentions 'special actions' but doesn't disclose critical behavioral traits like whether this is a destructive mutation, authentication requirements, rate limits, or error handling. The description is vague on what 'Update any user field' entails in practice, such as partial vs. full updates.

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 front-loaded with the core purpose and lists special actions efficiently in a single sentence. It avoids unnecessary fluff, though it could be slightly more structured (e.g., bullet points for actions) given the complexity of the tool.

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

Completeness2/5

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

For a complex mutation tool with 54 parameters, no annotations, and no output schema, the description is inadequate. It lacks information on behavioral context (e.g., side effects, permissions), response format, and error conditions, leaving significant gaps for an AI agent to operate safely and effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 76%, providing good documentation for most parameters. The description adds some value by highlighting 'special actions' (e.g., member_tag_action, credit_action), but doesn't explain parameter interactions or provide additional semantics beyond what's in the schema, such as how 'auto_geocode' relates to location fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Update') and resource ('existing member/user'), specifying it can update 'any user field' and lists special actions. It distinguishes from siblings like 'createUser' by focusing on updates, though it doesn't explicitly contrast with other update tools like 'updateUserMeta'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives (e.g., 'updateUserMeta' for metadata or 'createUser' for new users). It mentions 'special actions' but doesn't provide context on prerequisites, such as required permissions or when these actions apply, leaving usage unclear.

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