Uxia

Set Test Audience

set_test_audience

DestructiveIdempotent

Replace shared audience selections and participant counts; null clears. Use existing audience/tester IDs. Preserves blocks. No launch.

Input Schema

TableJSON Schema

Name	Required	Description
`testId`	Yes
`audience`	Yes
`construction`	No	Optional decisions; proposed wording stays separate. Acceptance needs current proposalRevision and matching saved wording. Never launch approval.
`expectedRevision`	No	Legacy compatibility only; ignored. The server resolves the current draft revision automatically.

Output Schema

TableJSON Schema

Name	Required	Description
`url`	No	Open the draft in Uxia.
`testId`	No
`blockId`	No	Server-assigned ID of the added block. Use it for subsequent edits and references.
`editable`	No
`definition`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 2, 2026

changedInput schema / properties / expectedRevision / description

Previous value: -"Current definition.revision. Reread on conflict; never retry blindly."New value: +"Legacy compatibility only; ignored. The server resolves the current draft revision automatically."

removedInput schema / properties / expectedRevision / exclusiveMinimum
```
Removed value: -0
```
addedInput schema / properties / expectedRevision / minimum
```
Added value: +0
```

changedInput schema / required

Previous value: -[
-  "expectedRevision",
-  "audience",
-  "testId"
-]New value: +[
+  "audience",
+  "testId"
+]

Changed1 schema field changedOct 1, 2026

addedOutput schema / properties / blockId

Added value: +{
+  "description": "Server-assigned ID of the added block. Use it for subsequent edits and references.",
+  "type": "string"
+}

Changed4 schema fields changedSep 30, 2026

changedInput schema / properties / audience / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "selections": {
-        "items": {
-          "additionalProperties": false,
-          "properties": {
-            "audienceId": {
-              "pattern": "^[a-fA-F0-9]{24}$",
-              "type": "string"
-            },
-            "requestedCount": {
-              "exclusiveMinimum": 0,
-              "type": "integer"
-            },
-            "selectedTesterIds": {
-              "items": {
-                "$ref": "#/properties/audience/anyOf/0/properties/selections/items/properties/audienceId"
-              },
-              "type": "array"
-            }
-          },
-          "required": [
-            "audienceId",
-            "requestedCount"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      }
-    },
-    "required": [
-      "selections"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "selections": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "audienceId": {
+              "pattern": "^[a-fA-F0-9]{24}$",
+              "type": "string"
+            },
+            "requestedCount": {
+              "exclusiveMinimum": 0,
+              "type": "integer"
+            },
+            "selectedTesterIds": {
+              "items": {
+                "pattern": "^[a-fA-F0-9]{24}$",
+                "type": "string"
+              },
+              "type": "array"
+            }
+          },
+          "required": [
+            "audienceId",
+            "requestedCount"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "selections"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / testId / $ref

Removed value: -"#/properties/audience/anyOf/0/properties/selections/items/properties/audienceId"

addedInput schema / properties / testId / pattern
```
Added value: +"^[a-fA-F0-9]{24}$"
```
addedInput schema / properties / testId / type
```
Added value: +"string"
```

First observedSep 28, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so safety is partly covered. The description still adds real value beyond them: "null clears" discloses a specific destructive behavior, "Preserves blocks" states what is not destroyed, and "No launch" scopes the side effects. It stops short of permissions or revision-conflict behavior, so not a 5.

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?

Four short front-loaded clauses with no filler; the primary action leads. The telegraphic style is efficient, though for a destructive operation a slightly more explicit sentence would aid comprehension.

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?

An output schema exists, so return values need no explanation. The description covers the destructive null-clears behavior, block preservation, and the no-launch boundary, which is sufficient for an agent to call it correctly against documented annotations.

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?

Schema coverage is only 50%, so the description must compensate. It usefully documents the null-clears semantics of audience and the must-be-existing constraint on audience/tester IDs, but adds nothing about construction or expectedRevision. Marginal value over the schema, so the baseline 3 fits.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (Replace) and resource (shared audience selections and participant counts), which cleanly separates it from siblings like create_audience (creation) and set_survey (different field). It does not explicitly name an alternative tool, but the purpose is unambiguous.

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?

"Use existing audience/tester IDs" gives an input precondition, and "No launch" implies the boundary against launch_test, but the description never states when to choose this tool versus alternatives such as create_audience or edit_draft_advanced. Usage is implied rather than spelled out.

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

All Uxia 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?