Skip to main content
Glama
Stellify-Software-Ltd

Stellify MCP Server

Official

update_element

Update a UI element by providing its UUID and a data object containing HTML attributes, classes, text, and event handlers. Supports Blade view naming and loop variable references.

Instructions

Update a UI element. Data object: tag, classes, text, event handlers (method UUIDs), classBindings. Set 'name' on root elements to create Blade views (e.g., name="notes.index" for view('notes.index')).

For elements inside @foreach loops (SSR/Blade): Use these attributes to reference the loop variable (defaults to $item):

  • textField: Field name for text content → outputs {{ $item->fieldName }}

  • hrefField: Field name for href → outputs href="{{ $item->fieldName }}" (field value ONLY, no prefix)

  • srcField: Field name for src → outputs src="{{ $item->fieldName }}"

For hrefs with path prefixes (IMPORTANT): hrefField outputs ONLY the field value. There is NO hrefPrefix attribute. For links like /post/slug-here, you MUST use hrefExpression:

  • hrefExpression: "/post/{{ $item->slug }}" → outputs href="/post/{{ $item->slug }}"

  • hrefExpression: "/category/{{ $item->slug }}" → outputs href="/category/{{ $item->slug }}"

For complex Blade expressions in attributes: Use expression attributes when you need more than simple field access:

  • hrefExpression: Blade expression for href → outputs href="..." with the expression

  • srcExpression: Blade expression for src → outputs src="..." with the expression

  • altExpression: Blade expression for alt → outputs alt="..." with the expression

Examples:

  • Path prefix: hrefExpression: "/post/{{ $item->slug }}"

  • Route helper: hrefExpression: "{{ route('posts.show', $item->slug) }}"

For Blade text content: Use the statements array with statement UUIDs containing Blade code. The statement's code property will be output directly for Blade to evaluate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uuidYesUUID of the element to update
dataYesHTML attributes and Stellify fields (tag, classes, text, classBindings, click, submit). Context fields: summary, rationale, references, decisions.
Behavior5/5

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

With no annotations, the description fully bears the burden of behavioral transparency. It discloses critical behaviors: setting 'name' creates Blade views, field attributes for foreach loops, hrefField outputs only the field value without prefix, and expression attributes are needed for complex Blade expressions. No contradictions exist.

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 wellstructured with clear headings and focused sections for different scenarios (foreach loops, href prefixes, complex expressions). While comprehensive, some repetition occurs (e.g., expression attributes for href, src, alt), but overall it is concise for the complexity involved.

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's complexity (nested data object, Bladespecific behaviors, no output schema), the description covers the main use cases thoroughly. It explains field attributes, expression attributes, and statements for Blade text. However, it omits error handling, validation details, and return behavior, which mildly reduces completeness.

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?

Schema coverage is 100% for both parameters (uuid and data), but the description adds substantial semantics: it details data object fields (tag, classes, text, event handlers, classBindings) and explains Bladespecific attributes and behaviors for loops and expressions. This goes far beyond the schema and is highly valuable.

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 UI element' and distinguishes this from create_element and delete_element by specifying fields like 'uuid' for updating and emphasizing modifications to existing elements. It provides a specific verb and resource.

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?

The description offers extensive guidance on when to use specific attributes (textField, hrefField, expressions) and conditions (foreach loops, href prefixes). It implicitly advises against using hrefField for prefixed paths and recommends hrefExpression instead. However, it lacks explicit 'when-not-to-use' or direct sibling comparisons.

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/Stellify-Software-Ltd/stellify-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server