Skip to main content
Glama

create_character_profile

Destructive

Create a local character reference profile for consistent image or video generation by storing asset IDs and training payloads; actual identity training is performed by a configured provider runner.

Instructions

Create a local character/identity reference profile for consistent image or video generation. Raven stores reference asset IDs and provider-training payloads; actual identity training happens only through a configured provider runner.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoOptional stable ID.
nameYesCharacter, spokesperson, founder, avatar, or product persona name.
metadataNoOptional non-secret metadata.
descriptionNoVisual/personality description.
consistency_notesNoWhat must stay consistent across generations.
reference_asset_idsYesRaven creative asset IDs for reference images/videos.
provider_training_idNoExternal provider training/character ID if already trained.
Behavior4/5

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

Annotations already indicate destructive action. Description adds context that actual identity training is external and only reference data is stored locally, which is beyond annotation signals.

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?

Two sentences, no redundancy. Front-loaded with purpose and immediately clarifies scope.

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?

Covers main behavioral context (local storage, no training), but lacks return value description since no output schema. Minor gap for a creation tool.

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?

All 7 parameters have schema descriptions (100% coverage), so baseline 3. Description does not add significant extra meaning beyond restating context like 'reference asset IDs'.

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?

Clearly states verb 'create', resource 'local character/identity reference profile', and purpose 'for consistent image or video generation'. Distinguishes from sibling tools by noting it is local and only stores references, not actual training.

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

Usage Guidelines3/5

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

Implied usage scenario (consistent generation), but no explicit when-to-use or when-not-to-use vs alternatives like create_brand_profile or create_generation_job.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rhinocap/raven-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server