Minds: Synthetic Market Research

Duplicate Study

duplicate_study

Copy a Study with all its questions and results over the same Audiences.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Name of the copy. Defaults to "<name> (copy)".
`studyId`	Yes	Study to duplicate; you must be able to open it. The private copy keeps every answer, chart, heatmap, summary and finished run; a schedule is copied paused. Audiences are shared, not copied (use duplicate_audience). Refused while a run is live.
`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 Study: id, name, createdAt and its Audiences with their Minds.
`workspaceUrl`	No	Minds workspace link for the new Study.
`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 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 / idempotencyKey / anyOf

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

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

removedOutput schema / properties / workspaceUrl / anyOf

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

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

AddedSep 30, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations declare non-read-only, non-destructive, non-idempotent, so the safety profile is partly covered. The description adds that questions and results are carried over, but omits the paused schedule, the audience-sharing behavior, the live-run refusal, and the retry semantics that the schema documents.

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 twelve-word sentence with the verb front-loaded and zero filler. It is efficient, though arguably too terse to carry any usage or behavioral context.

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 annotations carry the safety profile. However, for a mutation tool that can be refused (live run) and whose audience/idempotency behavior matters, the description leaves everything but the bare copy action to the schema.

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, studyId, idempotencyKey) are already documented in the schema. The description adds no parameter-level detail beyond what is structured, so the baseline 3 applies.

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?

States a specific verb (copy) and resource (Study) with scope ('all its questions and results over the same Audiences'). It does not name a sibling to differentiate from, though the 'same Audiences' phrasing implicitly separates it from duplicate_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?

Implies the use case is reproducing an existing study rather than creating one from scratch, but gives no explicit when/when-not guidance or prerequisites. The routing to duplicate_audience and the live-run refusal exist 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.