Skip to main content
Glama
brilliantdirectories

brilliant-directories-mcp

Official

updateTagGroup

Idempotent

Update an existing tag group record by ID, renaming it or clearing fields. Omitted fields are left untouched; changes are applied live.

Instructions

Update a tag group - Update an existing taggroup record by ID. Fields omitted are untouched. Writes live data.

Use when: renaming a tag group.

Required: id.

See also: createTagGroup (add new), deleteTagGroup (remove permanently).

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
group_tag_nameNo
_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?

Description adds context beyond annotations: 'Fields omitted are untouched' clarifies idempotent behavior, 'Writes live data' aligns with readOnlyHint=false, and return format is detailed. No contradiction.

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?

Concise, well-structured with 'Use when:', 'Required:', 'See also:', and 'Returns:' sections. 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?

Covers purpose, usage guidance, required fields, behavioral traits, return format, and special parameter details. Lacks explanation of group_tag_name, but overall sufficient for a 3-parameter tool with annotations.

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?

Only 33% schema coverage, but description compensates by explaining the _clear_fields mechanism and partial update behavior. However, group_tag_name parameter lacks any description in schema or text.

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 the verb 'Update' and the resource 'tag group', and distinguishes from siblings like createTagGroup and deleteTagGroup by mentioning them in 'See also'.

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

Usage Guidelines4/5

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

Provides explicit 'Use when:' guidance (renaming a tag group) and lists required parameter 'id'. 'See also' mentions alternatives. However, it could be more explicit about when not to use.

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