Orivox AI Website Builder

apply_dom_ops

Apply approved DOM operations to a project page and save.

Each operation is an object with an op (one of: set_text, replace_html, insert_before, insert_after, append_html, prepend_html, remove, set_attr, remove_attr, add_class, remove_class, move_before, move_after, move_to_page), a selector (CSS / #id / [data-ai-id='...']), and its payload (value|attr|html|target, all?). Unknown ops or extra fields are rejected (no partial write). Check changed in the result: False means the edit did not alter the page (no-op or refused by a safety guard -- see skip_warning).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	Yes
`operations`	Yes
`project_guid`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedAug 24, 2026

addedInput schema / properties / project_guid
```
Added value: +{
+  "type": "string"
+}
```
removedInput schema / properties / project_id
```
Removed value: -{
-  "type": "string"
-}
```

changedInput schema / required

Previous value: -[
-  "project_id",
-  "page",
-  "operations"
-]New value: +[
+  "project_guid",
+  "page",
+  "operations"
+]

First observedAug 4, 2026

TDQS

A4.4/5.0

Behavior5/5

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

With no annotations, the description carries the disclosure burden and does it well: it states that unknown ops or extra fields are rejected with 'no partial write', that 'changed' being False means a no-op or safety-guard refusal, and that a skip_warning may appear in the result. This gives real behavioral clarity beyond the schema.

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?

Purpose, operation format, validation behavior, and result semantics are each covered in just a few tightly packed sentences. Nothing is filler and the most important information is front-loaded.

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 complexity of 14 operation types, the description is robust: it lists op variants, rejection behavior, no-partial-write guarantee, changed-field interpretation, and skip_warning. Minor gaps are the exact payload shape per operation, but this is close to sufficient by itself with no annotations.

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 0%, so the description must compensate. It explains the operations array in depth: op enum values, selector syntax (CSS / #id / [data-ai-id='...']), and payload fields. It does not add much detail about project_guid/page beyond their obvious project/page context, but the critical inner-object semantics are well covered.

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?

States a specific verb and resource: 'Apply approved DOM operations to a project page and save.' It enumerates the valid op values, so an agent clearly understands the tool's edit-on-existing-page role and can distinguish it from sibling page-creation or build tools.

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 makes the use case clear: apply DOM operations to an existing project page and save. However, it never explicitly says when to use this over create_page, build_site, or publish_website, nor does it exclude cases like creating a new page.

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

All Orivox AI Website Builder tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?