Skip to main content
Glama

Minds: Synthetic Market Research

Create a Study

create_study
Idempotent

Creates a Study workspace from existing Audiences or inline Audience configurations. It does not ask questions or run research, and follow-up research inside an existing Study needs no new Study.

A Study with this exact name is named back and nothing is created, unless allowDuplicateName is true; work in that Study instead. Studies cannot be deleted here, so any extra Study is permanent.

Any request with two or more known questions belongs in one planned and confirmed multi-question block inside the Study, submitted once rather than as separate direct questions.

Creation is atomic and rolls back partial Audience failures. Studies are private; enabling link sharing also publishes the attached Audiences and their Minds. It does not change or replace an existing Study.

Input Schema

NameRequiredDescriptionDefault
nameYesName for the Study workspace (e.g., "Brand Perception Study", "Q4 Market Research")
audienceIdsNoPreferred field for existing Audience IDs to attach — use list_audiences to find IDs.
audienceConfigsNoPreferred field for new Audiences to create and attach atomically.
conversationFilesNoStimulus for the new Study, stored in Minds and returned as attachments (url, path) to pass with its questions. Respondents see a file only once a question carries it. Files shared in this conversation: uploaded or generated images, PDFs, documents. Each is copied into Minds storage on receipt; its file_id is its attachment id.
allowDuplicateNameNoCreate even though a Study with exactly this name exists. Only when the user asked for a separate Study with the same name.
isLinkSharingEnabledNoSet true ONLY when the user explicitly asked for a public/shareable Study link. Defaults to false: the Study is private to its owner and no share URL is generated. Enabling this ALSO publishes every attached Audience and every Mind inside them at world-readable URLs — including pre-existing Audiences passed via audienceIds. Do not enable it to "be helpful".

Output Schema

NameRequiredDescriptionDefault
nameNoStudy name.
studyIdNoCreated Study.
replayedNoTrue when an identical request returned the Study created earlier.
audiencesNoAudiences attached to the Study.
workspaceUrlNoAuthenticated Minds workspace link for the Study.
publicShareIdNoPublic share identifier, or null.
sharedStudyUrlNoPublic share link, or null when link sharing is off.
isLinkSharingEnabledNoWhether the public share link is on.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / allowDuplicateName
      Added value: +{
      +  "description": "Create even though a Study with exactly this name exists. Only when the user asked for a separate Study with the same name.",
      +  "type": "boolean"
      +}
  2. Changed14 schema fields changed
    • removedOutput schema / properties / isLinkSharingEnabled / anyOf
      Removed value: -[
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / isLinkSharingEnabled / type
      Added value: +[
      +  "boolean",
      +  "null"
      +]
    • removedOutput schema / properties / name / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / name / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / publicShareId / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / publicShareId / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / replayed / anyOf
      Removed value: -[
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / replayed / type
      Added value: +[
      +  "boolean",
      +  "null"
      +]
    • removedOutput schema / properties / sharedStudyUrl / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / sharedStudyUrl / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / studyId / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / studyId / 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"
      +]
  3. Changed1 schema field changed
    • addedInput schema / properties / conversationFiles
      Added value: +{
      +  "description": "Stimulus for the new Study, stored in Minds and returned as attachments (url, path) to pass with its questions. Respondents see a file only once a question carries it. Files shared in this conversation: uploaded or generated images, PDFs, documents. Each is copied into Minds storage on receipt; its file_id is its attachment id.",
      +  "items": {
      +    "properties": {
      +      "download_url": {
      +        "description": "Download URL the chat host supplies for this file.",
      +        "minLength": 1,
      +        "type": "string"
      +      },
      +      "file_id": {
      +        "description": "The chat host's ID for this file.",
      +        "minLength": 1,
      +        "type": "string"
      +      },
      +      "file_name": {
      +        "description": "File name when the host supplies it.",
      +        "minLength": 1,
      +        "type": "string"
      +      },
      +      "mime_type": {
      +        "description": "MIME type when the host supplies it.",
      +        "minLength": 1,
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "download_url",
      +      "file_id"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  4. Changed2 schema fields changed
    • removedInput schema / properties / groupConfigs
      Removed value: -{
      -  "description": "Legacy alias for audienceConfigs.",
      -  "items": {
      -    "properties": {
      -      "mindIds": {
      -        "items": {
      -          "type": "string"
      -        },
      -        "type": "array"
      -      },
      -      "name": {
      -        "type": "string"
      -      }
      -    },
      -    "type": "object"
      -  },
      -  "type": "array"
      -}
    • removedInput schema / properties / groupIds
      Removed value: -{
      -  "description": "Legacy alias for audienceIds.",
      -  "items": {
      -    "type": "string"
      -  },
      -  "type": "array"
      -}
  5. Changed1 schema field changed
    • 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 attached to the Study."
      +    },
      +    "isLinkSharingEnabled": {
      +      "anyOf": [
      +        {
      +          "type": "boolean"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "Whether the public share link is on."
      +    },
      +    "name": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "Study name."
      +    },
      +    "publicShareId": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "Public share identifier, or null."
      +    },
      +    "replayed": {
      +      "anyOf": [
      +        {
      +          "type": "boolean"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "True when an identical request returned the Study created earlier."
      +    },
      +    "sharedStudyUrl": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "Public share link, or null when link sharing is off."
      +    },
      +    "studyId": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "Created Study."
      +    },
      +    "workspaceUrl": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "Authenticated Minds workspace link for the Study."
      +    }
      +  },
      +  "type": "object"
      +}
  6. Changed1 schema field changed
    • changedInput schema / properties / audienceConfigs / items / properties / mindIds / description
      Previous value: -"Mind IDs to add to this Audience — use list_minds to find IDs."New value: +"IDs of existing Minds to add to this Audience."
  7. Changed1 schema field changed
    • removedInput schema / properties / groupConfigs / items / properties / sparkIds
      Removed value: -{
      -  "description": "Legacy alias for mindIds.",
      -  "items": {
      -    "type": "string"
      -  },
      -  "type": "array"
      -}
  8. Changed5 schema fields changed
    • changedInput schema / properties / groupConfigs / description
      Previous value: -"Legacy alias for audienceConfigs. Accepted for compatibility."New value: +"Legacy alias for audienceConfigs."
    • removedInput schema / properties / groupConfigs / items / properties / mindIds / description
      Removed value: -"Mind IDs to add to this Audience — use list_minds to find IDs"
    • removedInput schema / properties / groupConfigs / items / properties / name / description
      Removed value: -"Audience name (optional — defaults to \"Audience N\"). E.g., \"Gen Z Consumers\", \"Marketing Experts\""
    • changedInput schema / properties / groupConfigs / items / properties / sparkIds / description
      Previous value: -"Legacy alias for mindIds. Accepted for back-compat."New value: +"Legacy alias for mindIds."
    • changedInput schema / properties / groupIds / description
      Previous value: -"Legacy alias for audienceIds. Accepted for compatibility."New value: +"Legacy alias for audienceIds."
  9. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations declare readOnlyHint=false, openWorldHint=true, idempotentHint=true and destructiveHint=false; the description goes well beyond them by disclosing atomic rollback of partial Audience failures, that Studies cannot be deleted (extra Studies are permanent), and that link sharing publishes attached Audiences and their Minds at world-readable URLs. The duplicate-name no-op is consistent with the idempotent hint rather than contradicting it.

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?

Purpose is front-loaded in the first sentence and each subsequent paragraph addresses a distinct decision (duplicates, research routing, atomicity, sharing). It is slightly long and the closing sentence ('does not change or replace an existing Study') partly repeats earlier points.

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?

With an output schema available, the description needn't explain returns, and it still covers the aspects structured fields cannot: permanence of created Studies, atomic rollback, privacy side effects of link sharing, and duplicate handling. Nothing an agent needs to call this safely 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% and the schema already carries the key per-parameter warnings (including the isLinkSharingEnabled publishing caveat and the audienceIds/audienceConfigs preference). The description adds routing context around allowDuplicateName and multi-question submission but little parameter-level syntax or defaults beyond what the schema documents, so the baseline 3 applies.

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 ("Creates a Study workspace") plus the two source modes (existing Audiences or inline Audience configurations). It also carves out the boundary against siblings ask_audience/ask_study/run_study_questions by saying it does not ask questions or run research.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-not guidance (no research inside it; follow-up research in an existing Study needs no new Study), duplicate-name routing (use the existing Study unless allowDuplicateName is true), and a directive that requests with two or more known questions belong in one planned multi-question block. An agent can distinguish this from plan_study_questions and ask_study from the text alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.