READ

get_persona

Fetch a single persona by UUID — their sketch in full, with goals, frustrations, behaviours, proficiency, devices, quote and archive stamp.

Fetch one persona in full once list_personas has named it, or once a story's persona_id has: the whole sketch the analyst wrote, to keep in view while drafting the story, the acceptance criteria or the test that serves this person. A persona outside the token's team or project scope, or one the person cannot see, answers RESOURCE_NOT_FOUND, never a permission error, so existence does not leak.

Requires ability

The token behind the MCP session must hold it, or the call is refused with TOKEN_MISSING_ABILITY.

The REST endpoint and this tool share one action, so validation, permissions and events are identical.

Annotations

Read-only

It reads and never changes anything.

Arguments

persona_id*string

UUID of the persona to fetch.

What it returns

{  "data": {    "id": "b8c9d0e1-f2a3-4b4c-9d5e-6f7a8b9c0d12",    "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",    "name": "Busy Buyer",    "tagline": "Orders for three branches between meetings.",    "role_title": "Procurement officer",    "demographics": "<p>Mid-forties, twelve years at the company, works from the regional office.</p>",    "goals": "<ul><li>Reorder last month's basket in two minutes.</li></ul>",    "frustrations": "<ul><li>Has to call support to change a delivery address.</li></ul>",    "behaviours": "<p>Works on a laptop at the desk and a phone on the warehouse floor.</p>",    "tech_proficiency": "medium",    "devices": ["Laptop", "Phone"],    "quote": "Just let me repeat last month's order.",    "position": 0,    "archived_at": null,    "created_at": "2026-10-20T09:20:00+00:00",    "updated_at": "2026-10-27T11:30:00+00:00"  },  "meta": {}}

How it fails

RESOURCE_NOT_FOUND

unknown persona_id, or a persona outside the token's scope or the person's visibility.

TOKEN_MISSING_ABILITY

token lacks persona:view.

How is this guide?

Last updated on