Skip to main content
Glama
brilliantdirectories

brilliant-directories-mcp

Official

updateTagRelationship

Idempotent

Update an existing tag relationship record by ID, altering only the specified fields while leaving others untouched.

Instructions

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

Use when: adjusting a tag-relationship record's metadata.

Required: id.

See also: createTagRelationship (add new), deleteTagRelationship (remove permanently).

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
object_idNoPrimary key of the record being tagged. Which table it lives in depends on tag_type_id - look up via listTagTypes. For tag_type_id=1 (Users), object_id is a user_id from users_data.
_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?

Adds value beyond annotations by stating 'Fields omitted are untouched', 'Writes live data', and the exact return format. No contradiction with annotations (readOnlyHint=false, destructiveHint=false).

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?

Exceptionally concise: a single sentence followed by bullet points for use, required, see also, and returns. No redundant information; every sentence serves a purpose.

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?

For an update tool with 3 well-documented parameters and comprehensive annotations, the description covers purpose, usage guidance, required inputs, return format, and behavioral notes (e.g., untouched fields). No output schema needed as return is stated.

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?

Schema coverage is 67%, and the description adds context like the return format and the behavioral rule that omitted fields are untouched, which helps interpret parameter usage. The description doesn't repeat schema details but provides essential context.

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 explicitly states 'Update a tag relationship - Update an existing tagrelationship record by ID', providing a specific verb and resource. It distinguishes from siblings via 'See also: createTagRelationship (add new), deleteTagRelationship (remove permanently).'

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?

Clear guidance with 'Use when: adjusting a tag-relationship record's metadata' and 'Required: id'. The see also section effectively steers the agent to alternatives, though explicit 'when not to use' is absent.

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