Minds: Synthetic Market Research

Duplicate Audience

duplicate_audience

Copy an Audience with independent copies of its Minds and all they know.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Name of the copy. Defaults to "<name> (copy)".
`audienceId`	Yes	Audience to duplicate; you must be able to edit it. The copy is private and gets new Minds (profiles, knowledge, embeddings) plus the grounding, sources, formations and finished validations; it counts against the Mind allowance. While the Audience is still being built the copy is its last good state; copied members without a working version are retrained on their own.
`idempotencyKey`	No	Retry key. Without one, an identical call within 15 minutes returns the same copy instead of a second one; send a new key only to deliberately make another copy of the same source with the same name.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	No	The new Audience: id, name, mindCount, mindIds, minds and sharing state (always private).
`audienceUrl`	No	Minds workspace link for the new Audience.
`idempotencyKey`	No	Key of this duplication; reuse it to retry without creating a second copy.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 11, 2026

changedInput schema / properties / audienceId / description

Previous value: -"Audience to duplicate; you must be able to edit it. The copy is private and gets new Minds (profiles, knowledge, embeddings) plus the grounding, sources, formations and finished validations; it counts against the Mind allowance. Refused while the Audience is still being built."New value: +"Audience to duplicate; you must be able to edit it. The copy is private and gets new Minds (profiles, knowledge, embeddings) plus the grounding, sources, formations and finished validations; it counts against the Mind allowance. While the Audience is still being built the copy is its last good state; copied members without a working version are retrained on their own."

Changed1 schema field changedOct 6, 2026

changedInput schema / properties / idempotencyKey / description

Previous value: -"Retry key. Reuse the key a failed or timed-out call returned so the retry cannot create a second copy."New value: +"Retry key. Without one, an identical call within 15 minutes returns the same copy instead of a second one; send a new key only to deliberately make another copy of the same source with the same name."

Changed4 schema fields changedOct 2, 2026

removedOutput schema / properties / audienceUrl / anyOf

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

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

removedOutput schema / properties / idempotencyKey / anyOf

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

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

AddedSep 30, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations declare this as a non-read-only, non-destructive write. The description adds context beyond that: the copy is a deep, independent replica of the Minds rather than a link, so the source is unaffected. It does not mention the copy being private, counting against the Mind allowance, or retraining of copied members, all of which live only in 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single tight sentence with the core operation front-loaded and no filler. It is efficient, though arguably under-specified rather than optimally balanced for a mutation tool with this many siblings.

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 values need not be explained, and the schema is fully self-documented. What is missing is purely descriptive routing and precondition context for a write operation that sits among many similar-sounding siblings.

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 all three parameters (name, audienceId, idempotencyKey) are already documented with substantial detail in the schema. The description adds no parameter-level information, which is the expected baseline when structured fields do the work.

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 (copy an Audience) and immediately scopes what is copied (independent copies of its Minds and all they know), which cleanly separates it from the sibling duplicate_study. An agent can identify the operation without opening the schema.

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?

The description gives no when-to-use, when-not-to-use, or alternative routing, which matters in a fleet of ~35 siblings that include create_audience_from_brief and duplicate_study. Any preconditions (edit rights, Mind allowance) appear only in the schema, not the description.

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.