Skip to main content
Glama

KanbanMCP

Update a persona

update_persona
DestructiveIdempotent

Changes one persona's name, title, description or brief. Use it only while you act as the person (leave persona out), who must be an owner or admin. A connection that acts as a persona cannot use it. Use it after the person sees the text and says yes. It never changes whether a persona may mark work done.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "target": "<target>"
    },
    "name": "update_persona"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoThe new name.
briefNoThe whole new brief, in markdown. It replaces the old one.
titleNoThe new title.
targetYesThe persona to change: its name or id.
descriptionNoWhat the persona is for. Other agents read it in the team list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description adds real value on top: authorization requirements, the acting-as-persona restriction, and a scope boundary ("never changes whether a persona may mark work done"). It also notes brief replacement overwrites the old value, though it says nothing about reversibility of other fields.

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?

Front-loaded with the action, then constraints. Sentences each carry weight, though the trailing "never changes whether a persona may mark work done" is somewhat oblique and requires domain knowledge to parse.

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?

For a destructive, idempotent update with no output schema, the description covers authorization, actor restrictions, the approval precondition, and scope limits. Nothing an agent needs to invoke it correctly 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%, so the baseline is 3. The description lists the mutable fields but adds little beyond the schema, and the phrase "leave persona out" refers to a persona context parameter that is not present in this schema, which adds mild ambiguity rather than clarity.

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

Purpose4/5

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

Names a specific verb+resource ("Changes one persona's name, title, description or brief") and enumerates the editable fields. It does not explicitly distinguish itself from the sibling set_brief, which also touches briefs, so sibling separation is implied rather than stated.

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 prerequisites (must be acting as the person, who must be an owner or admin), an exclusion (a connection acting as a persona cannot use it), and a workflow condition (use after the person approves the text). This is close to a full when/when-not specification.

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.

Resources