Skip to main content
Glama

Minds: Synthetic Market Research

List Audiences

list_audiences
Read-onlyIdempotent

For a listing or search reply, include both the returned top-level workspaceUrl and each listed Audience's workspaceUrl verbatim as full visible link text: scheme, query and trailing slash. Item links do not replace the list-level link. Lists owned Audiences newest first with counts and sharing. workspaceUrl opens the owner's workspace; sharedAudienceUrl is public. addOnRequired omits links/commercial details; use an available Audience. First-page openDrafts: rework matching drafts or recalibrate matching Audiences before a new brief.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_audiences"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoAudiences per page, most recently updated first (default 20, max 100).
offsetNoNumber of Audiences to skip; pass nextOffset from the previous page to continue.
searchQueryNoFilters by name (case-insensitive, all matches, paged with limit/offset); the closest name when nothing matches. Omit to browse.
includeMindsNoAlso return each Audience's member Minds (id, name, discipline). Default false: Audiences carry a Mind count only.

Output Schema

NameRequiredDescriptionDefault
limitNoPage size used.
offsetNoOffset of this page.
audiencesNoAudiences: id, name, workspaceUrl, mindCount, sharing state, and member Minds when includeMinds was set.
nextOffsetNoOffset of the next page; absent on the last page.
openDraftsNoFirst page only: the caller's open, unconfirmed Audience drafts (id, name, status, sha256, revision, memberCount, createdAt, updatedAt), newest first. Rework the matching one by id and sha256 instead of starting a new brief.
shownCountNoNumber of items in this response.
totalCountNoTotal number of items available.
workspaceUrlNoMinds workspace link.
duplicateNamesNoNames shared by several of the caller's Audiences on this page: name and the ids carrying it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / openDrafts
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {},
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "First page only: the caller's open, unconfirmed Audience drafts (id, name, status, sha256, revision, memberCount, createdAt, updatedAt), newest first. Rework the matching one by id and sha256 instead of starting a new brief."
      +}
  2. Changed1 schema field changed
    • addedOutput schema / properties / duplicateNames
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {},
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Names shared by several of the caller's Audiences on this page: name and the ids carrying it."
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / searchQuery / description
      Previous value: -"Search for an Audience by name (fuzzy matching supported). Returns the best match."New value: +"Filters by name (case-insensitive, all matches, paged with limit/offset); the closest name when nothing matches. Omit to browse."
  4. Changed12 schema fields changed
    • removedOutput schema / properties / limit / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / limit / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / nextOffset / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / nextOffset / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / offset / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / offset / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / shownCount / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / shownCount / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / totalCount / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / totalCount / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / workspaceUrl / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / workspaceUrl / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  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: id, name, workspaceUrl, mindCount, sharing state, and member Minds when includeMinds was set."
      +    },
      +    "limit": {
      +      "anyOf": [
      +        {
      +          "type": "number"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "Page size used."
      +    },
      +    "nextOffset": {
      +      "anyOf": [
      +        {
      +          "type": "number"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "Offset of the next page; absent on the last page."
      +    },
      +    "offset": {
      +      "anyOf": [
      +        {
      +          "type": "number"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "Offset of this page."
      +    },
      +    "shownCount": {
      +      "anyOf": [
      +        {
      +          "type": "number"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "Number of items in this response."
      +    },
      +    "totalCount": {
      +      "anyOf": [
      +        {
      +          "type": "number"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "Total number of items available."
      +    },
      +    "workspaceUrl": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "description": "Minds workspace link."
      +    }
      +  },
      +  "type": "object"
      +}
  6. Changed4 schema fields changed
    • addedInput schema / properties / includeMinds
      Added value: +{
      +  "description": "Also return each Audience's member Minds (id, name, discipline). Default false: Audiences carry a Mind count only.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Audiences per page, most recently updated first (default 20, max 100).",
      +  "maximum": 100,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Number of Audiences to skip; pass nextOffset from the previous page to continue.",
      +  "maximum": 9007199254740991,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • changedInput schema / properties / searchQuery / description
      Previous value: -"Search for an Audience by name (fuzzy matching supported)"New value: +"Search for an Audience by name (fuzzy matching supported). Returns the best match."
  7. Added

TDQS

B3.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the bar is lower, yet the description still adds substantive context: only owned Audiences, newest-first ordering, counts and sharing included, workspaceUrl versus sharedAudienceUrl meaning, addOnRequired suppressing links and commercial details, and the first-page openDrafts quirk. That is genuine behavior disclosure beyond structured fields.

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

Conciseness2/5

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

The lead sentence is a link-markup directive rather than the tool's purpose, so the definition is not front-loaded. The remainder is a chain of semicolon-joined fragments ('sharedAudienceUrl is public. addOnRequired omits links/commercial details') that require re-reading, and the opening formatting rule is verbose relative to its value.

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 and key fields (workspaceUrl, sharedAudienceUrl, addOnRequired, openDrafts) need not be fully documented here, and the description does touch on them. Still missing is guidance on search-versus-browse behavior, pagination flow, and how this listing relates to the audience attach/recalibrate tools an agent will likely chain into.

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 already explains limit, offset, searchQuery, and includeMinds in detail, making the baseline 3. The description adds no parameter-level meaning at all — no mention of paging with nextOffset, case-insensitive name matching, or what includeMinds returns — so it neither compensates nor detracts.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The core statement 'Lists owned Audiences newest first with counts and sharing' is a specific verb plus resource with ordering and scope, but it is the third sentence, buried behind output-formatting instructions about workspaceUrl link text. Nothing distinguishes it from sibling listing tools such as list_formations, list_studies, or list_study_drafts, so an agent must infer from the name alone.

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?

There is conditional guidance — when addOnRequired appears, 'use an available Audience', and on a first page with openDrafts, rework or recalibrate before a new brief — which implies real workflow contexts. However, it never states when to call this versus a sibling listing tool, nor when to supply searchQuery instead of browsing; that only exists in the schema.

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.