Uxia

Create Audience

create_audience

Create a new audience in the caller's Uxia workspace and synchronously generate AI testers for it. An audience defines targeting filters (age, gender, geography, demographics) used to generate synthetic AI tester profiles, not recruit people. Returns the created audience plus the freshly generated testers.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No
`count`	No	How many AI testers to generate. Defaults to 5, which is the minimum a test can launch with — an audience with fewer approved testers is rejected at launch.
`roles`	No
`gender`	Yes
`ageRange`	Yes	Two-element [min, max] age range (integers, 16-100).
`countries`	No
`languages`	No
`industries`	No
`isReusable`	No
`description`	No
`techLiteracy`	No
`customDetails`	No
`maritalStatus`	No
`nationalities`	No
`educationLevel`	No
`personalIncome`	No
`householdIncome`	No
`employmentStatus`	No
`languagesRequirement`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`testers`	No	Freshly generated AI testers for the new audience.
`audience`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 15, 2026
- changedInput schema / properties / ageRange / description
```
Previous value: -"Two-element [min, max] age range (integers, 0-120)."New value: +"Two-element [min, max] age range (integers, 16-100)."
```
- changedInput schema / properties / ageRange / items / maximum
```
Previous value: -120New value: +100
```
- changedInput schema / properties / ageRange / items / minimum
```
Previous value: -0New value: +16
```
Changed6 schema fields changedSep 30, 2026
- removedInput schema / properties / personalIncome / properties / range / $ref
```
Removed value: -"#/properties/householdIncome/properties/range"
```
- addedInput schema / properties / personalIncome / properties / range / description
```
Added value: +"Two-element [min, max] range in the given currency."
```
- addedInput schema / properties / personalIncome / properties / range / items
```
Added value: +{
+  "maximum": 500000,
+  "minimum": 0,
+  "type": "number"
+}
```
- addedInput schema / properties / personalIncome / properties / range / maxItems
```
Added value: +2
```
- addedInput schema / properties / personalIncome / properties / range / minItems
```
Added value: +2
```
- addedInput schema / properties / personalIncome / properties / range / type
```
Added value: +"array"
```
First observedSep 28, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations cover the safety profile (not read-only, not idempotent, not destructive). The description adds genuinely useful context beyond that: creation happens synchronously and the operation also generates tester profiles, which signals a potentially slow/expensive call and that repeat calls produce new resources. It omits auth/permission prerequisites but is otherwise solidly transparent.

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?

Three tightly written sentences with the core action and the crucial "not recruit people" clarification front-loaded. No filler, no restatement of the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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-value detail is not required, and annotations carry the safety profile. However, for a 19-parameter creation tool the definition leaves most parameter semantics and all when-to-use routing unaddressed, making it only adequately complete.

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

Parameters2/5

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

Schema description coverage is only 11% across 19 parameters, so the description must compensate and largely does not. Naming the filter categories (age, gender, geography, demographics) maps to a few params, but roles, techLiteracy, maritalStatus, employmentStatus, income objects, isReusable, customDetails, and languagesRequirement receive no semantic explanation anywhere.

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 ("Create a new audience") and immediately clarifies what an audience is here — targeting filters for synthetic AI testers, "not recruit people." This distinctly separates it from siblings like list_audiences and set_test_audience.

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?

Explains the domain concept and disambiguates "audience" from human recruiting, but never states when to call this versus siblings such as list_audiences (discovery) or set_test_audience (binding an existing audience to a test). Usage is implied rather than instructed.

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?