Skip to main content
Glama
brilliantdirectories

brilliant-directories-mcp

Official

updateReview

Idempotent

Update an existing review by ID to change its status (accept, decline, pending) or correct text fields. Ideal for moderation and typo fixes.

Instructions

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

Use when: moderating - change review_status (0=Pending -> 2=Accepted to publish, 3=Declined to reject, 4=Waiting for Admin). Also used for admin corrections of typos in review text.

Required: review_id.

Enums: review_status: 0=Pending, 2=Accepted, 3=Declined, 4=Waiting for Admin.

See also: createReview (add new), deleteReview (remove permanently).

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
review_idYes
review_nameNo
review_titleNo
review_descriptionNo
rating_overallNo
recommendNo
review_statusNoReview status (integer): - `0` = Pending (awaiting moderation) - `2` = Accepted (visible on profile) - `3` = Declined (rejected, not public) - `4` = Waiting for Admin (member pre-accepted, needs admin sign-off) Value `1` is NOT documented. BD does NOT reject it - stores `"1"` verbatim with undefined render behavior. Stick to documented values. Normal flow: `0` -> `2` (accepted) or `0` -> `3` (declined).
_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?

Beyond annotations, the description adds key behaviors: 'Writes live data', 'Fields omitted are untouched', the effect of _clear_fields, and the return format. This fully informs the agent of operational implications.

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 well-structured with bold headings and concise bullet points. It covers essential information without excessive verbosity, though a slightly tighter organization could improve readability.

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?

Despite many parameters, the description covers purpose, usage, key parameters, return value, and relationships to sibling tools. The missing output schema is mitigated by specifying the return format. The context is sufficient for effective tool invocation.

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 description coverage is only 25%, but the description compensates by explaining review_status enum values and the moderation flow, and provides detailed semantics for _clear_fields. However, other parameters (review_name, etc.) lack additional meaning.

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 tool updates an existing review record by ID, specifying that omitted fields remain untouched. It distinguishes itself from createReview and deleteReview, making the purpose unambiguous.

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?

Provides explicit guidance on when to use the tool: for moderating review_status changes and for admin corrections. It also highlights the required review_id and references sibling tools (createReview, deleteReview), making usage context clear.

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