OnlyWorlds

update_element

Update an existing element by type and id, changing ONLY the fields you pass — omitted fields are preserved.

This is a server-side read-merge: the current element is loaded and only the keys in fields are applied, so it is safe against the raw-HTTP-PATCH hazard where sending a partial link array replaces the whole array. Semantics per field kind: a text field you pass is set (pass an empty string "" to clear it); a multi-link field you pass REPLACES that field's array wholesale (pass an empty array [] to clear it) — for additive/subtractive link edits that leave the rest of the array intact, use edit_links instead. type is a slug from list_element_types; id is the element's UUID. Requires a WRITE API-Key. Returns the full updated element in the v2 wire shape. Errors if the element does not exist, or (naming the field) on an unknown field or a bad link target.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`type`	Yes
`fields`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A5/5.0

Behavior5/5

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

Details server-side read-merge safety, field semantics (text vs link), error conditions, and required WRITE API-Key despite no annotations.

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?

Well-structured, front-loaded with purpose, detailed yet concise sentences, no wasted words.

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?

Covers prerequisites, side effects, error cases, and sibling relationships; output schema exists so return shape is not needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds full meaning to id (UUID), type (slug from list_element_types), and fields (behavior per field kind), compensating for 0% schema coverage.

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?

Explicitly states updating an existing element by type and id, with clear distinction from siblings like create_element and edit_links.

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 when-to-use vs alternatives (edit_links for link arrays) and references list_element_types for type.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All OnlyWorlds tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0

Disambiguation5/5

Each tool targets a distinct operation: batch vs single creation, link editing, schema retrieval, search across types or fields, etc. No two tools overlap in purpose.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in snake_case (e.g., bulk_apply, get_element, list_element_types), making the set predictable.

Tool Count5/5

With 11 tools, the server covers creation, reading, updating, schema introspection, search, and a change feed without being bloated or under-scoped.

Completeness3/5

The tool set lacks a delete operation; neither a dedicated delete_element nor a delete option in bulk_apply exists. While link editing and partial updates are well-handled, the inability to remove elements is a notable gap.

Resources

Need Help?