Skip to main content
Glama
brilliantdirectories

brilliant-directories-mcp

Official

updatePage

Modify page content, SEO settings, layout, and visibility for custom pages, search results, or widget pages in Brilliant Directories websites.

Instructions

Update a page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seo_idYesPage primary key (required to identify record)
seo_typeNoPage type identifier. These are the values BD customers can choose from in admin:\n content = Single Web Page (USE THIS for custom/landing/static pages — it is the default)\n data_category = Post Search Results\n profile_search_results = Member Search Results\n custom_widget_page = Custom Widget as Web Page\n password_retrieval_page = Password Retrieval Page\n unsubscribed = Unsubscribed Page\nWhen a user asks for a "landing page", "static page", "about page", "contact page", or any generic custom page, always use "content".\nNote: the underlying BD system has additional internal seo_type values (home, profile, payment, etc.) that are system-seeded and should NOT be created via API — customers never have a reason to call createPage with those.
filenameNoURL slug (e.g. home, about-us)
nicknameNoHuman-readable label shown in admin panel
titleNoHTML title tag — supports template tokens like %%%website_name%%%
meta_keywordsNoMeta keywords — supports template tokens
meta_descNoMeta description — supports template tokens
seo_textNoAdditional SEO body text rendered on page
h1NoH1 heading — supports template tokens
h2NoH2 heading — supports template tokens
breadcrumbNoBreadcrumb label
contentNoMain HTML body — supports [widget=Name] shortcodes and template tokens
content_footerNoAdditional HTML below main content
content_activeNo1 = active, 0 = hidden
content_menuNoMenu section this page belongs to
content_orderNoSort order within menu/section
content_groupNoAdmin-panel grouping label
content_layoutNoFull-screen page width toggle (integer boolean).\n 1 = Full Screen Page Width (page content spans the full viewport width, no side margins)\n 0 = Standard width (default — page content is constrained to the site theme's content column)\nIn BD admin this is a single checkbox. Pass 1 to enable, 0 to disable. If unsure, omit the field and the default will apply.
content_sidebarNoSidebar configuration or widget shortcode
menu_layoutNoSidebar position and width (integer). Only has an effect when the page has a sidebar configured — on pages without a sidebar this field is ignored.\n 1 = Left Wide (sidebar on the left, wide column)\n 2 = Right Wide (sidebar on the right, wide column)\n 3 = Left Slim (sidebar on the left, narrow column)\n 4 = Right Slim (sidebar on the right, narrow column)\nDefault: 1 (Left Wide). Note the ordering is NOT sequential by side — left positions are 1 and 3, right positions are 2 and 4.\nDespite the field name, this is the SIDEBAR position setting, not a navigation menu layout — the name is a historical BD artifact.
show_formNo1 = show contact form
form_nameNoForm slug to render when show_form is enabled
hide_from_menuNo1 = hide from navigation menus
hide_header_linksNo1 = hide header navigation links
hide_headerNo1 = hide site header
hide_footerNo1 = hide site footer
hide_top_rightNo1 = hide top-right header area
facebook_titleNoOpen Graph title for social sharing
facebook_descNoOpen Graph description
facebook_imageNoOpen Graph image URL
org_templateNoTemplate/layout ID
allowed_productsNoComma-separated plan/product IDs (empty = all plans)
enable_hero_sectionNo"1" = enable hero section
hero_imageNoHero background image URL
hero_section_contentNoHero HTML content
hero_alignmentNoHero alignment
hero_link_textNoHero CTA link text
hero_link_urlNoHero CTA link URL
hero_link_target_blankNoopen in new tab
linked_post_typeNoLinked post type
linked_post_categoryNoLinked post category
private_page_selectNoAccess control setting
page_render_widgetNoWidget ID to render as page content
Behavior1/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but fails completely. It doesn't indicate whether this is a mutation operation (implied by 'update' but not confirmed), what permissions are required, whether changes are reversible, what happens to unspecified fields, or any rate limits/constraints. For a tool with 43 parameters that presumably modifies website content, this lack of behavioral context is critical.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is maximally concise at just three words ('Update a page'), with zero wasted language. While this conciseness comes at the cost of completeness, the description itself is perfectly structured and front-loaded with the core action.

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

Completeness1/5

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

Given the tool's complexity (43 parameters, mutation operation, no annotations, no output schema), the description is completely inadequate. It doesn't explain what 'page' means in this context, what system this operates on, what the typical use cases are, what happens after update, or any error conditions. For such a complex tool with significant behavioral implications, this minimal description fails to provide necessary context.

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?

The description adds no parameter information beyond what's already in the schema, which has 100% coverage with detailed descriptions for all 43 parameters. While the schema does excellent work documenting each field, the description doesn't provide any higher-level guidance about parameter relationships, common usage patterns, or which fields are most important. The baseline score of 3 reflects adequate schema coverage without description enhancement.

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

Purpose2/5

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

The description 'Update a page' is a tautology that merely restates the tool name without providing any meaningful context about what kind of page is being updated or what aspects can be modified. While the input schema reveals this is about SEO/content pages with numerous fields, the description itself offers no specific verb+resource differentiation or indication of scope beyond the obvious.

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

Usage Guidelines1/5

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

The description provides absolutely no guidance on when to use this tool versus alternatives like createPage or deletePage, nor does it mention any prerequisites, dependencies, or contextual considerations. With 43 sibling tools including createPage and deletePage, the lack of any comparative guidance is a significant omission.

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