Skip to main content
Glama

persona_create

创建自定义 Persona

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": "persona_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
photo_urlNo
callback_idNo自定义追踪 ID,会在 `/openapi/v1/work/status` 的结果里原样回传,用于对回你自己的业务单号(暂不支持 webhook 推送)
voice_audio_urlNo可选,用于语音克隆

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / callback_id / description
      Previous value: -"自定义追踪 ID,webhook URL 后台配置"New value: +"自定义追踪 ID,会在 `/openapi/v1/work/status` 的结果里原样回传,用于对回你自己的业务单号(暂不支持 webhook 推送)"
  2. First observed

TDQS

C2.6/5.0
Behavior3/5

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

The annotations already disclose a non-readonly, non-idempotent, open-world write that is not destructive, so the safety profile is covered. The description adds nothing beyond that: it does not say whether creation is synchronous, whether the `callback_id` implies asynchronous tracking, or what state a newly created Persona starts in.

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

Conciseness3/5

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

The definition is a single short phrase with no filler, which is technically concise, but it is under-specified rather than efficient. There is no structure to front-load because nothing beyond the tool name is conveyed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a write tool whose annotations are present but sparse and that has no output schema, the definition does not give the agent enough information to call it correctly. It omits what a Persona represents, whether voice cloning requires `voice_audio_url`, what the response returns, and how to track the result such as through `get_persona_status`.

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

Parameters2/5

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

Schema coverage is only 50%: `callback_id` and `voice_audio_url` are documented inline, but `name` and `photo_url` are not. The description supplies no parameter meaning at all, not even for the undocumented fields, and it does not explain why zero parameters are required for a create operation.

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 description states a verb and resource (create a custom Persona), so the basic operation is identifiable. However, it is essentially a restatement of the tool name `persona_create` with the modifier '自定义', and it never explains what a Persona is, what it will be used for, or how it differs from the `ai_actor_*` tools in the sibling list.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool rather than the alternatives, and no indication that `persona_list` or `get_persona_status` should be used for later steps. No prerequisites, limits, or exclusions are mentioned, so the agent must infer the entire workflow from sibling names.

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