Skip to main content
Glama
brilliantdirectories

brilliant-directories-mcp

Official

updateState

Idempotent

Update a state record to correct its details. Specify location_id and only fields to change; omitted fields remain untouched.

Instructions

Update a state (corrections only) - Update a state row. Read-mostly - use for corrections. Fields omitted are untouched (PATCH semantics - only send what you want to change).

Required: location_id.

Warning on state_filename: it's the URL slug in every search page using this state. Rename -> broken URLs + orphaned SEO pages. Create redirects if you must.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
location_idYes
state_snNo
state_lnNo
state_filenameNoURL slug. Rename breaks inbound URLs - create redirects.
country_snNo
_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?

Beyond annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true), the description adds key behaviors: PATCH semantics ('Fields omitted are untouched'), the warning about state_filename breaking URLs, and the 'corrections only' nature. These details help the agent understand side effects and safe usage.

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 concise and front-loaded with purpose. It uses clear formatting with bold and warning. The only redundancy is 'Update a state (corrections only) - Update a state row.' Overall, it is well-structured and free of unnecessary text.

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 the tool has 6 parameters, annotations, and no output schema, the description covers purpose, PATCH semantics, required field, and a critical warning. It misses guidance on usage relative to siblings and detailed field meanings, but for a PATCH update tool, it is reasonably complete and actionable.

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 PATCH semantics (fields omitted untouched) and warns about state_filename, which adds value beyond the schema. However, with only 33% schema description coverage, other parameters (state_sn, state_ln, country_sn) lack explanation in the description. The baseline is 3 due to low coverage, and the description 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 a state (corrections only) - Update a state row.' This specifies the verb (update) and resource (state), and adds 'corrections only' to distinguish from general updates. The purpose is unambiguous and differentiates from sibling update* tools for other resources.

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

Usage Guidelines3/5

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

The description says 'Read-mostly - use for corrections' and warns about state_filename renaming, implying when to use (corrections) and what to avoid (renaming without redirects). However, it does not explicitly state when not to use this tool or suggest alternatives, leaving room for improvement.

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