Skip to main content
Glama

levea-mcp-server

by io.github.brajendrak00068
OverviewDiscussionsAdmin

queue_edit

Fire-and-forget async path. Returns immediately with a taskId. Use when the edit may exceed the MCP request timeout (long viral-clip generation, multi-format export). Poll with check_task_status or get_active_task.

Input Schema

NameRequiredDescriptionDefault
sceneNoOptional existing scene/timeline state to continue editing (advanced).
assetsNoOptional asset descriptors. Each item: { id?, type: "video"|"image"|"audio", url|src, mimeType?, duration? }.
promptYesNatural-language description of the desired edit or creative brief. The backend planner decomposes it into canonical actions (viral clips, captions, reframe, export, …). Send the user's intent verbatim — do not pre-decompose into multiple calls.
brandIdNoOptional brand-profile id to apply for this call (palette, fonts, logo, voice, gradeBias). Look up ids via list_brand_kits. Overrides project default brand.
core_onlyNoIf true, response carries only rendering-essential scene fields (no debug metadata).
video_urlNoOptional source video URL. Auto-seeded as the starting layer when no scene is provided.
editedPlanNoOptional pre-edited plan object returned by a prior awaiting_approval response.
project_idNoOptional project id for tracking / continuity.
flaggedIssuesNoOptional list of specific user-flagged problems for this run (e.g. ["caption #3 misspelled"]).
workingMemoryNoWorking-memory snapshot returned by a prior call (typically one that returned awaiting_approval). Re-sending resumes that run.
attachedImagesNoOptional base64-encoded reference images the agent should consider while planning.
projectBrandIdNoOptional default brand for the project. Persists; per-call brandId overrides.
captionTemplateModeNoHow to apply captionTemplatePreset.
requirePlanApprovalNoIf true, the agent stops after planning and returns { status: "awaiting_approval", workingMemory, plan } without mutating. Resume by re-calling with the returned workingMemory + an approval prompt ("yes", "approve", "do it").
captionTemplatePresetNoOptional caption template slug to apply when (re)generating captions. One of 41 builtins (hormozi, mrbeast, viral-pop, minimal-pro, karaoke, neon-pop, typewriter, pop-wave, subtitle-bar, creator-box, …) or a user-saved template id from list_caption_templates.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

No annotations are provided, so the description must carry the full behavioral disclosure; it does the most important part by stating the fire-and-forget contract, the immediate taskId return, and the polling follow-up. It omits failure/cancellation behavior and says nothing about the awaiting_approval resume loop, which the schema covers.

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?

There are three short sentences with no padding: the async contract comes first, the timeout trigger comes second, and the polling next step comes last. Each sentence earns its place, and the content is front-loaded.

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

Completeness3/5

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

For a 15-parameter tool with no output schema, the description covers the async contract and the polling path, which is the critical missing context. However, it does not position the tool against autonomous_edit or autonomous_edit_streaming, or against the awaiting_approval/workingMemory resume path, which is a substantial part of this tool's behavior.

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%, and all 15 parameters are documented in the schema, including requirePlanApproval, workingMemory, and brandId. The description adds no parameter-level meaning beyond noting that a taskId is returned, so the baseline of 3 applies.

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?

The description states that this is a fire-and-forget async editing path that returns immediately with a taskId, and it frames the tool's role clearly enough to distinguish it from synchronous edit tools. Sibling tools such as autonomous_edit and autonomous_edit_streaming are not named, so the statement that it is a 'different kind' of edit tool is only implied.

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

Usage Guidelines4/5

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

This is where 'Use when the edit may exceed the MCP request timeout (long viral-clip generation, multi-format export)' appears, and it provides concrete triggers. It does not say when not to use this tool; for example, when to choose the streaming or synchronous sibling instead remains unstated.

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

All levea-mcp-server toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources