Minds: Synthetic Market Research

List Study Drafts

list_study_drafts

Read-onlyIdempotent

Lists a page of unfinished Study draft summaries, newest first, or returns the complete saved planning state for one exact draft ID. Draft records are distinct from running or completed studies.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Drafts per page, newest first (default 20, max 50).
`offset`	No	Number of drafts to skip; pass nextOffset from the previous page to continue.
`draftId`	No	Exact study draft ID to retrieve with its complete saved planning state. Omit to list draft summaries.
`searchQuery`	No	Case-insensitive part of the draft name; returns every match, paged.

Output Schema

TableJSON Schema

Name	Required	Description
`draft`	No	The requested draft with its complete saved planning state, or null.
`limit`	No	Page size used.
`drafts`	No	One page of resumable draft summaries, without saved planning state.
`offset`	No	Offset of this page.
`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.
`searchQuery`	No	The name search this page answers.

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedOct 7, 2026

changedInput schema / properties / draftId / description

Previous value: -"Exact study draft ID to retrieve. Omit to list all resumable study drafts owned by the authenticated user."New value: +"Exact study draft ID to retrieve with its complete saved planning state. Omit to list draft summaries."

addedInput schema / properties / limit

Added value: +{
+  "description": "Drafts per page, newest first (default 20, max 50).",
+  "maximum": 50,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / offset

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

addedInput schema / properties / searchQuery

Added value: +{
+  "description": "Case-insensitive part of the draft name; returns every match, paged.",
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}

changedOutput schema / properties / draft / description

Previous value: -"The requested draft, or null."New value: +"The requested draft with its complete saved planning state, or null."

changedOutput schema / properties / drafts / description

Previous value: -"Resumable drafts."New value: +"One page of resumable draft summaries, without saved planning state."

addedOutput schema / properties / limit

Added value: +{
+  "description": "Page size used.",
+  "type": [
+    "number",
+    "null"
+  ]
+}

addedOutput schema / properties / nextOffset

Added value: +{
+  "description": "Offset of the next page; absent on the last page.",
+  "type": [
+    "number",
+    "null"
+  ]
+}

addedOutput schema / properties / offset

Added value: +{
+  "description": "Offset of this page.",
+  "type": [
+    "number",
+    "null"
+  ]
+}

addedOutput schema / properties / searchQuery

Added value: +{
+  "description": "The name search this page answers.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / shownCount

Added value: +{
+  "description": "Number of items in this response.",
+  "type": [
+    "number",
+    "null"
+  ]
+}

changedOutput schema / properties / totalCount / description

Previous value: -"Number of drafts returned."New value: +"Total number of items available."

Changed2 schema fields changedOct 2, 2026
- removedOutput schema / properties / totalCount / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / totalCount / type
```
Added value: +[
+  "number",
+  "null"
+]
```

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "draft": {
+      "description": "The requested draft, or null."
+    },
+    "drafts": {
+      "anyOf": [
+        {
+          "items": {},
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Resumable drafts."
+    },
+    "totalCount": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Number of drafts returned."
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedAug 25, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / draftId / pattern

Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"

AddedJul 31, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds the newest-first ordering and the draft-vs-study distinction, which is genuine value, but says nothing about pagination behavior or cursor semantics beyond what the schema states.

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?

Two sentences, zero waste, and the dual behavior is front-loaded so an agent immediately knows both modes. Every clause earns its place.

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

Completeness4/5

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

With an output schema present and rich annotations, the description needn't explain return values, and it correctly focuses on the two modes plus the draft/study distinction. It is essentially complete, missing only explicit routing to sibling tools.

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 fully documents limit, offset, draftId, and searchQuery. The description reinforces draftId's role ('complete saved planning state') and ordering, but adds little meaning beyond the schema. 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 and resource ('Lists a page of unfinished Study draft summaries' / 'returns the complete saved planning state for one exact draft ID') and covers both operating modes. It distinguishes drafts from running/completed studies, which separates it conceptually from list_studies, but never names sibling tools explicitly.

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?

The two modes are implied (paginated list vs. single-draft retrieval) and the distinction from running/completed studies gives some selection context. However it never names alternatives like list_studies or save_study_draft, and gives no explicit when-not guidance.

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.