Skip to main content
Glama

List personas

list_personas
Read-onlyIdempotent

Retrieve personas from Persona Studio as read-only JSON, optionally scoped to a workspace and capped by a row limit, to inspect available personas before generating or fetching individual records.

Instructions

List personas from Persona Studio. Use generate_persona to create one, list_shadow_personas for Shadow Personas, and get_studio_entity for one row. Read-only. Returns JSON items up to limit.

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_personas"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum rows. Integer from 1 to 500. Default 100.
workspaceNoOptional Studio workspace name, slug or id from list_workspaces. Omit for the active workspace.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv6.3.0
    • addedInput schema / properties / workspace
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Optional Studio workspace name, slug or id from list_workspaces. Omit for the active workspace.",
      +  "title": "Workspace"
      +}
  2. Changed1 schema field changedv6.2.1
    • addedInput schema / properties / limit / description
      Added value: +"Maximum rows. Integer from 1 to 500. Default 100."
  3. Addedv6.1.5

TDQS

A4.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so 'Read-only' merely restates structured data. The one piece of added context is 'Returns JSON items up to limit', which hints at truncation behaviour, but there is no mention of pagination, ordering, or what happens when the limit truncates results.

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?

Three short sentences, front-loaded with the purpose, followed by sibling routing and return behaviour. No filler and nothing buried.

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?

For a simple two-parameter, read-only list tool with an output schema and full schema coverage, the description supplies everything needed to select and invoke it. It only omits result-set semantics such as ordering, which is a minor gap given the output schema exists.

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% – limit (1-500, default 100) and workspace (name, slug or id, omit for active workspace) are fully documented in the schema. The description's 'up to limit' adds no meaning beyond that, so the baseline of 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?

The description names a specific verb and resource ('List personas from Persona Studio') and immediately separates it from three siblings: generate_persona for creation, list_shadow_personas for shadow personas, and get_studio_entity for a single row. An agent can choose between them without opening a schema.

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 routing guidance is given for the main alternatives: create via generate_persona, shadow variants via list_shadow_personas, single-row lookup via get_studio_entity. This covers both when to use this tool and when to use something else instead.

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