Skip to main content
Glama

Minds: Synthetic Market Research

List Audiences

list_audiences
Read-onlyIdempotent

Lists the authenticated user's Audiences, most recently updated first, one page at a time (limit, default 20, and offset; nextOffset continues), with Mind counts, sharing state, and workspace or shared links. includeMinds adds each Audience's member Minds. searchQuery returns the best fuzzy name match instead of a page. Each Audience carries a workspaceUrl, the authenticated workspace link that stays valid verbatim, plus the top-level workspaceUrl for the Audience list; sharedAudienceUrl, when present, is the public share link for recipients.

Input Schema

TableJSON 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.
searchQueryNoSearch for an Audience by name (fuzzy matching supported). Returns the best match.
includeMindsNoAlso return each Audience's member Minds (id, name, discipline). Default false: Audiences carry a Mind count only.

Output Schema

TableJSON 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.
shownCountNoNumber of items in this response.
totalCountNoTotal number of items available.
workspaceUrlNoMinds workspace link.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
      +}
  2. 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."
  3. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds substantial behavioral context beyond that: one-page-at-a-time pagination with nextOffset continuation, 'most recently updated first' ordering, searchQuery returning the best fuzzy match 'instead of a page,' and the nuance that workspaceUrl stays valid verbatim while sharedAudienceUrl is the public share link.

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 dense paragraph with no filler, front-loaded with the core list behavior before parameter and URL details. The heavy parenthetical style makes it slightly harder to parse than a bulleted structure, but every clause earns its place and nothing is wasted.

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 annotations covering the safety profile, the description covers scope, ordering, pagination, returned fields, both optional parameters, and URL semantics. Only edge-case behavior (e.g., empty searchQuery results or no matching names) is left unspecified, which is a minor gap for an otherwise complete read-only tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already documents all four parameters (100% coverage), so the baseline is 3. The description adds cross-parameter semantics the schema cannot express: searchQuery overrides pagination rather than filtering within it, includeMinds extends each Audience with member Minds, and nextOffset serves as the continuation cursor. This meaningfully exceeds the baseline.

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?

The description names a specific verb (Lists), resource (the authenticated user's Audiences), and ordering (most recently updated first), which clearly distinguishes it from siblings such as list_studies, export_audience, and ask_audience. Its scope, pagination, and optional-behavior details make the purpose unambiguous even before consulting the schema.

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

Usage Guidelines4/5

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

The description establishes clear context: this is the paginated-listing tool for the user's own Audiences, with searchQuery and includeMinds as behavioral alternatives. However, it never names a sibling explicitly or states a 'when not to use' condition, so exclusion guidance is implied rather than stated.

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.