Minds: Synthetic Market Research

List Study Templates

list_study_templates

Read-onlyIdempotent

Lists your own and team-shared Study templates, most used first, as a page of summaries (templateId, name, revision, method, question count), or returns one exact templateId with its revision, research method, questions, response settings and question attachments. configuration.questions is a fixed, pre-registered instrument and configuration.methodId the research method it runs with; both can be planned as they are.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Templates per page, most used first (default 20, max 50).
`offset`	No	Number of templates to skip; pass nextOffset from the previous page to continue.
`templateId`	No	Exact template to return in full. Omit to list template summaries.
`searchQuery`	No	Case-insensitive part of the template name; returns every match, paged.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	No	One page of template summaries (id, name, revision, methodId, questionCount), or the complete template requested by templateId.
`limit`	No	Page size used.
`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.

Changed11 schema fields changedOct 7, 2026

addedInput schema / properties / limit

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

addedInput schema / properties / offset

Added value: +{
+  "description": "Number of templates 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 template name; returns every match, paged.",
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}

changedInput schema / properties / templateId / description

Previous value: -"Omit to list your own and team-shared Study templates."New value: +"Exact template to return in full. Omit to list template summaries."

changedOutput schema / properties / data / description

Previous value: -"Study templates."New value: +"One page of template summaries (id, name, revision, methodId, questionCount), or the complete template requested by templateId."

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"
+  ]
+}

addedOutput schema / properties / totalCount

Added value: +{
+  "description": "Total number of items available.",
+  "type": [
+    "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": {
+    "data": {
+      "description": "Study templates."
+    }
+  },
+  "type": "object"
+}

AddedSep 15, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real context beyond that: ordering ('most used first'), paged summaries, and the note that configuration.questions is a pre-registered instrument with configuration.methodId as its method.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

Reasonably front-loaded with the core listing behavior, but the second sentence about configuration.questions and configuration.methodId is dense and jargon-heavy, diluting an otherwise tight definition.

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?

An output schema exists, so return-value detail isn't required from the description. Combined with annotations covering the safety profile and a 100%-covered input schema, the description covers listing, filtering, paging, and single-record retrieval adequately.

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 baseline is 3. The description reinforces templateId's dual role and mentions paging/search context, but adds little syntax or meaning beyond what limit, offset, templateId, and searchQuery already document.

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 (Lists) and resource (Study templates), and clearly covers both modes: a page of summaries or one exact template by templateId. The scope 'your own and team-shared' is useful. It does not explicitly differentiate itself from siblings like list_studies or list_study_drafts, leaving that distinction to the reader.

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?

It describes the two behaviors (list summaries vs. fetch one by templateId) so the choice between modes is implied by whether templateId is given. However, there is no explicit when-to-use guidance relative to list_studies, list_study_drafts, or manage_study_template.

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.