Models and parameters

Model availability changes faster than a static documentation page. Before setting model, read the generation tool's input schema from MCP tools/list. Its enum, description, default, compatible modes, resolutions, durations, and other limits are authoritative.

Select a model only when necessary

1. Read the target tool's live schema.
2. Omit model for the current default unless the job requires a named capability such as edit mode, a specific duration, or a particular output resolution.
3. Validate the whole combination—model, mode, duration, aspect ratio, resolution, and references—against the same schema.
4. Render a cheap proof before raising quality, resolution, duration, or the number of outputs.

Selection is complete when every requested parameter is accepted by one model without relying on clamping or an undocumented fallback.

Image generation

advibly_generate_image exposes the current image-model enum. The main cost-driving parameters are:

Use medium quality while exploring and raise it only for a final asset when the selected model supports that value.

Video generation

advibly_generate_video exposes each current video model plus the allowed mode, duration, resolution, and media-reference fields. Video is normally priced by output duration and capability tier; resolution and model choice can multiply the result.

Different models support different combinations. Do not copy a resolution or mode from one model to another without checking the live schema.

When a video setting fails repeatedly, return to the default model and one of its documented combinations, then reintroduce one override at a time.

Talking actors and audio

• advibly_generate_talking_video lists its current engines, actors, supported resolutions, and duration rules.
• advibly_generate_voiceover and advibly_generate_music expose their current voices, models, and length constraints through their schemas.
• advibly_list_actors returns the actor IDs accepted by talking-video calls.

Fixed and utility operations

Operations such as video analysis, stitching, subtitles, and composition rendering have their own schemas and pricing behavior. Use the tool description returned by tools/list, then check Credit costs before a large workflow.