Skip to main content
Glama
brilliantdirectories

brilliant-directories-mcp

Official

updateEmailTemplate

Idempotent

Modify specific fields of an existing email template by ID, leaving omitted fields unchanged to update subject, body, wrapper, triggers, or category.

Instructions

Update an email template - Update an existing emailtemplate record by ID. Fields omitted are untouched. Writes live data.

Use when: editing any field on an existing template — subject, body, wrapper mode (notemplate), category, signature, triggers, etc. Mirrors createEmailTemplate field-for-field; only email_id is required.

Required: email_id.

Enums (same as createEmailTemplate): signature: 0/1; notemplate: 0 (logo left), 2 (logo center), 3 (logo right), 4 (template, no logo), 1 (plaintext-only, no wrapper); category_id: 0/1/3/4/15/16 (unrestricted on update); unsubscribe_link: 0/1.

See also: createEmailTemplate (add new), deleteEmailTemplate (remove permanently).

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
email_idYes
email_nameNoInternal name for this email template (used by `[email-template name=...]` references and admin lookups). **Lowercase, hyphens, no spaces** (e.g. `welcome-email`, `password-reset`, `lead-notification-admin`) — see **Rule: Email template recipe**.
email_subjectNoSupports merge tags
email_bodyNoContent-only HTML — BD wraps it in the document scaffold. Open with any content tag (`<p>`, `<table>`, `<div>`, `<h1>`/`<h2>`, `<img>`, etc.). Inline `style=""` only — no `<style>` blocks (Outlook strips them) and no `class=""` (emails have no site stylesheet). Gradients need a fallback `background-color:` first. Verify image URLs return 200 before embedding when possible. Supports `%%%merge_tag%%%` tokens and `[widget=Name]` shortcodes. See **Rule: Email template recipe**.
email_typeNo
triggersNoComma-separated events
websiteNo0=platform-wide
email_fromNo
priorityNo
signatureNoAppend the site's default email signature to this template. Set to `1` to include the site signature; BD appends it automatically at send time.
category_idNoTemplate category. `update` is unrestricted across `0`/`1`/`3`/`4`/`15`/`16`. (On `create`, only `0` is allowed — other values are system-populated.)
notemplateNoTemplate + logo wrapper mode. `0` = template + logo left; `2` = template + logo center; `3` = template + logo right; `4` = template, no logo; `1` = no template or logo (plaintext-only). When this is anything other than `1`, BD's global template wraps `email_body` in a 600px-wide containing table — do NOT add your own outer max-width wrapper in that case.
content_typeNo
unsubscribe_linkNo
_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"]`.
Behavior4/5

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

Annotations already indicate readOnlyHint=false, destructiveHint=false, idempotentHint=true. Description adds 'Fields omitted are untouched' for partial update behavior and 'Writes live data' for immediacy, providing context beyond annotations. 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.

Conciseness5/5

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

Highly structured with clear sections: purpose, use-when, required, enums, see-also, returns. Every sentence is informative and no unnecessary words.

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

Completeness4/5

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

Given 15 parameters and no output schema, the description provides a solid overview, enum details, and return format. It references external rules but otherwise covers key aspects. Could be slightly more detailed on return behavior beyond the message.

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 coverage is 60%. Description explains enums for signature, notemplate, category_id, and unsubscribe_link, and describes _clear_fields. However, parameters like email_type, website, email_from, priority, content_type lack elaboration in description, so it partially compensates but not fully.

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 an email template' and explains the action (update by ID), resource (email template), and key behavior (fields omitted are untouched, writes live data). It distinguishes from siblings like createEmailTemplate and deleteEmailTemplate.

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?

Explicit 'Use when:' section lists scenarios (editing subject, body, wrapper mode, etc.) and contrasts with create/delete tools via 'See also:' references. Required parameter specified.

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