Minds: Synthetic Market Research

List Audiences

list_audiences

Read-onlyIdempotent

Lists the authenticated user's Audiences, most recently updated first, one page at a time (limit, default 20, and offset; nextOffset continues), with Mind counts, sharing state, and links. includeMinds adds each Audience's member Minds. searchQuery filters by name (case-insensitive, all matches, paged). Each Audience's workspaceUrl is the authenticated workspace link, valid verbatim; sharedAudienceUrl, when present, is the public share link for recipients. addOnRequired marks a paid Marketplace Audience the user has not subscribed to: prefer the user's own Audiences, and only use it after the user subscribes.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Audiences per page, most recently updated first (default 20, max 100).
`offset`	No	Number of Audiences to skip; pass nextOffset from the previous page to continue.
`searchQuery`	No	Filters by name (case-insensitive, all matches, paged with limit/offset); the closest name when nothing matches. Omit to browse.
`includeMinds`	No	Also return each Audience's member Minds (id, name, discipline). Default false: Audiences carry a Mind count only.

Output Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Page size used.
`offset`	No	Offset of this page.
`audiences`	No	Audiences: id, name, workspaceUrl, mindCount, sharing state, and member Minds when includeMinds was set.
`nextOffset`	No	Offset of the next page; absent on the last page.
`shownCount`	No	Number of items in this response.
`totalCount`	No	Total number of items available.
`workspaceUrl`	No	Minds workspace link.
`duplicateNames`	No	Names shared by several of the caller's Audiences on this page: name and the ids carrying it.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026

addedOutput schema / properties / duplicateNames

Added value: +{
+  "anyOf": [
+    {
+      "items": {},
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Names shared by several of the caller's Audiences on this page: name and the ids carrying it."
+}

Changed1 schema field changedOct 7, 2026

changedInput schema / properties / searchQuery / description

Previous value: -"Search for an Audience by name (fuzzy matching supported). Returns the best match."New value: +"Filters by name (case-insensitive, all matches, paged with limit/offset); the closest name when nothing matches. Omit to browse."

Changed12 schema fields changedOct 2, 2026

removedOutput schema / properties / limit / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / limit / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / nextOffset / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / nextOffset / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / offset / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / offset / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / shownCount / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / shownCount / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / totalCount / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / totalCount / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / workspaceUrl / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / workspaceUrl / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "audiences": {
+      "anyOf": [
+        {
+          "items": {},
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Audiences: id, name, workspaceUrl, mindCount, sharing state, and member Minds when includeMinds was set."
+    },
+    "limit": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Page size used."
+    },
+    "nextOffset": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Offset of the next page; absent on the last page."
+    },
+    "offset": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Offset of this page."
+    },
+    "shownCount": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Number of items in this response."
+    },
+    "totalCount": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Total number of items available."
+    },
+    "workspaceUrl": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Minds workspace link."
+    }
+  },
+  "type": "object"
+}

Changed4 schema fields changedSep 18, 2026

addedInput schema / properties / includeMinds

Added value: +{
+  "description": "Also return each Audience's member Minds (id, name, discipline). Default false: Audiences carry a Mind count only.",
+  "type": "boolean"
+}

addedInput schema / properties / limit

Added value: +{
+  "description": "Audiences per page, most recently updated first (default 20, max 100).",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / offset

Added value: +{
+  "description": "Number of Audiences to skip; pass nextOffset from the previous page to continue.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

changedInput schema / properties / searchQuery / description

Previous value: -"Search for an Audience by name (fuzzy matching supported)"New value: +"Search for an Audience by name (fuzzy matching supported). Returns the best match."

AddedAug 27, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Annotations already cover the read-only/idempotent/non-destructive profile, yet the description adds substantial behavioral context beyond them: page-at-a-time iteration via limit/offset/nextOffset, most-recently-updated ordering, name-filter matching rules, and the meaning of output fields like workspaceUrl (valid verbatim), sharedAudienceUrl, and addOnRequired.

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?

A single dense paragraph that is front-loaded with the core purpose and iteration model before drilling into filter and field semantics. Every sentence carries information, though it is tightly packed for one block of prose.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Even though an output schema exists and return values needn't be explained, the description goes further by clarifying ambiguous output fields (workspaceUrl vs sharedAudienceUrl, addOnRequired) and the pagination contract. Nothing an agent needs to call this correctly is missing.

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 the schema already documents all four parameters including defaults, ranges, and nextOffset continuation. The description largely restates these (limit default 20, offset/nextOffset, includeMinds adds member Minds), adding little syntax or meaning the schema does not already carry.

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 with scope: 'Lists the authenticated user's Audiences', and adds ordering and pagination semantics up front. It is immediately distinguishable from siblings like list_studies or list_study_drafts, which operate on different resources.

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?

Gives some operational guidance ('Omit to browse' for searchQuery, default includeMinds=false) and a directive about addOnRequired ('prefer the user's own Audiences, and only use it after the user subscribes'). However, this is guidance about interpreting results rather than explicit when-to-use/when-not and no alternative sibling is named.

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

All Minds: Synthetic Market Research 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.