Rawa

List audiences

list_audiences

Read-onlyIdempotent

The brand's audiences: target profiles with an optional age range, gender and language that override the brand's markets, voice and photography. An empty markets, brandVoice or photographyGuidelines inherits the brand's; an empty ageRange, gender or language means any. Returns truncated when there are more than limit.

Input Schema

Name	Required	Description	Default
`limit`	No	How many to return. Defaults to 25.
`brandId`	No	A brand id from get_workspace or list_brands, or the brand's name. Omit it when the organization has a single brand.

Output Schema

Name	Required	Description	Default
`audiences`	Yes
`truncated`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026

changedInput schema / properties / brandId / description

Previous value: -"A brand id from get_workspace or list_brands. Omit it when the organization has a single brand."New value: +"A brand id from get_workspace or list_brands, or the brand's name. Omit it when the organization has a single brand."

Changed3 schema fields changedOct 27, 2026

addedOutput schema / properties / audiences / items / properties / ageRange

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "max": {
+      "type": "number"
+    },
+    "min": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / audiences / items / properties / gender

Added value: +{
+  "enum": [
+    "women",
+    "men"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / audiences / items / properties / language

Added value: +{
+  "description": "The language the audience reads, e.g. 'Arabic'.",
+  "type": "string"
+}

First observedOct 23, 2026

TDQS

B3.1/5.0

Behavior4/5

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

Beyond the read-only/idempotent annotations, the description discloses meaningful data semantics: empty markets, brandVoice, or photographyGuidelines inherit the brand's values, empty ageRange/gender/language means any, and results truncate beyond limit. This adds real interpretive context for the returned audiences.

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 compact and front-loads the domain concept of audiences. It is dense but every clause carries inheritance or truncation information, with no filler.

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 structure need not be explained. However, for a listing tool the description lacks explicit operation framing and when-to-use context, leaving some ambiguity despite strong domain semantics.

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 description coverage is 100%, so both parameters are already documented. The description adds a bit of meaning by explaining truncation relative to limit, but gives no further guidance on brandId semantics beyond what the schema already states.

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

Purpose3/5

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

The description names the resource ("The brand's audiences") and implies retrieval through "Returns truncated", but never states the verb or operation explicitly. An agent can infer listing, yet it is not as clear as siblings like list_brands that encode the action in the name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus alternatives such as get_competitor_audience or list_brands. It also does not mention prerequisites, such as when brandId can be omitted, despite that being documented only in the schema.

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

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