Skip to main content
Glama
brilliantdirectories

brilliant-directories-mcp

Official

updateMembershipPlan

Idempotent

Update an existing membership plan by ID to adjust pricing, toggle new-signup availability, or change feature flags. Changes apply to new signups; existing members retain original terms.

Instructions

Update a membership plan - Update an existing membershipplan record by ID. Fields omitted are untouched. Writes live data.

Use when: adjusting pricing (monthly_amount/yearly_amount), toggling sub_active (new-signup availability), or changing feature flags like searchable, photo_limit. Changes apply to NEW signups; existing members on this plan keep their original terms unless manually migrated.

Required: subscription_id.

See also: createMembershipPlan (add new), deleteMembershipPlan (remove permanently).

Returns: { status: "success", message: {...updatedRecord} } - the full updated record after changes applied.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subscription_idYes
subscription_nameNo
monthly_amountNo
yearly_amountNo
sub_activeNoPlan availability for NEW signups: - `1` = active (plan appears on public signup pages; new members can join) - `0` = inactive (plan hidden from new-signup flows; existing members on this plan keep it — grandfather behavior) Use this to retire a plan cleanly. Do NOT hack the signup widget markup to hide a plan.
searchableNoWhether members on this plan appear in public member search results. `1`=visible in search, `0`=hidden. Use this to hide a membership tier from public listings without deactivating billing.
hide_initial_amountNoPayment-cycle visibility toggle: hide the one-time/initial-amount option from PUBLIC checkout pages. `0`=shown publicly (default), `1`=hidden publicly; when hidden, the cycle is still available when an admin manually creates a subscription inside the BD admin area (admin-only).
hide_monthly_amountNoPayment-cycle visibility toggle: hide the monthly option from PUBLIC checkout pages. `0`=shown publicly (default), `1`=hidden publicly; when hidden, still available for admin-created subscriptions.
hide_quarterly_amountNoPayment-cycle visibility toggle: hide the quarterly option from PUBLIC checkout pages. `0`=shown publicly (default), `1`=hidden publicly; when hidden, still available for admin-created subscriptions.
hide_semiyearly_amountNoPayment-cycle visibility toggle: hide the semi-yearly (6-month) option from PUBLIC checkout pages. `0`=shown publicly (default), `1`=hidden publicly; when hidden, still available for admin-created subscriptions.
hide_yearly_amountNoPayment-cycle visibility toggle: hide the yearly option from PUBLIC checkout pages. `0`=shown publicly (default), `1`=hidden publicly; when hidden, still available for admin-created subscriptions.
hide_biennially_amountNoPayment-cycle visibility toggle: hide the biennially (2-year) option from PUBLIC checkout pages. `0`=shown publicly (default), `1`=hidden publicly; when hidden, still available for admin-created subscriptions.
hide_triennially_amountNoPayment-cycle visibility toggle: hide the triennially (3-year) option from PUBLIC checkout pages. `0`=shown publicly (default), `1`=hidden publicly; when hidden, still available for admin-created subscriptions.
hide_billing_linksNoVisibility toggle for billing/transaction links in the member dashboard for this plan. `0`=show billing links (default), `1`=hide billing links (e.g. free plans or admin-managed-only plans where members shouldn't self-manage billing).
hide_parent_accountsNoVisibility toggle for parent-account elements when this plan supports sub-accounts. `0`=show, `1`=hide.
hide_reviews_rating_optionsNoVisibility toggle for review rating controls on this plan's member profiles. `0`=show ratings UI, `1`=hide ratings UI.
hide_specialtiesNoVisibility toggle for specialties/categories section on this plan's member profiles. `0`=show, `1`=hide.
hide_notificationsNoVisibility toggle for notification UI in the member dashboard for this plan. `0`=show, `1`=hide.
subscription_filenameNoOptional URL slug for this plan's public page. Must be site-wide unique — duplicates cause URL routing conflicts. Pre-check with 5 filtered `list*` calls (each `property_value=<proposed>&property_operator==`): `listMembershipPlans`+`subscription_filename` (ignore hits on this plan's own `subscription_id`), `listTopCategories`+`filename`, `listSubCategories`+`filename`, `listWebPages`+`filename`, `listUsers`+`filename`. Any OTHER hit = taken. Safe to leave blank.
custom_checkout_urlNoOptional custom checkout URL for this plan. Stored in `users_meta` (`database=subscription_types`, `key=custom_checkout_url`); MCP wrapper handles EAV upsert on update. Must be unique across all plans. Pre-check: `listUserMeta(database="subscription_types", key="custom_checkout_url")` then client-filter for any row whose `value` matches yours; ignore the row where `database_id` equals this plan's `subscription_id`. Any OTHER hit = taken. Safe to leave blank.
_clear_fieldsNoColumn names to clear to empty string. Available on every `update*` operation. Works on base columns AND EAV/`users_meta` rows (rows preserved with `value=""`). To actually clear a field you MUST use this parameter — sending the field with `""` alone is a no-op (BD drops empty values). To remove a `users_meta` row entirely, use `deleteUserMeta`. See **Rule: Clearing fields**. Example: `_clear_fields: ["h2", "hero_link_url"]`.
Behavior5/5

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

Discloses that changes only affect new signups (grandfathering), writes live data, and describes return format. Annotations (idempotentHint=true, openWorldHint=true) are consistent, and description adds critical context beyond them, such as the effect on existing members.

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 moderately long but well-structured with bold headings and bullet points. Every sentence serves a purpose—usage scenarios, required param, return format, parameter groups, and clear-field rule. Some details (like uniqueness check procedure) are verbose but justified by parameter complexity.

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 21 parameters, no output schema, and good annotations, the description covers all critical aspects: purpose, usage context, required param, return structure, behavioral side effects (grandfathering), and clearing fields. It fully compensates for the missing output schema by describing the return format.

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 schema description coverage is 81% (extensive per-param docs), the description adds value by grouping param purposes ('pricing', 'toggling sub_active'), explaining `_clear_fields` behavior, and providing uniqueness checks for `subscription_filename` and `custom_checkout_url`. This goes beyond simply restating 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 'Update a membership plan' and specifies it updates by ID, distinguishing it from create and delete siblings. It uses specific verbs ('adjust', 'toggle', 'change') and resource, making purpose unmistakable.

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 provides 'Use when:' scenarios (pricing, sub_active, feature flags), required parameter 'subscription_id', and 'See also' linking to create/delete alternatives. This gives clear guidance on when to invoke.

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