chore(luma): verify sync with Docs OpenAPI spec — no changes needed#8
Draft
chore(luma): verify sync with Docs OpenAPI spec — no changes needed#8
Conversation
Copilot
AI
changed the title
[WIP] Sync luma service with updated documentation
chore(luma): verify sync with Docs OpenAPI spec — no changes needed
Apr 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Triggered by automated Docs sync issue for the
lumaservice. Audited the currentopenapi/luma.jsonspec against the luma MCP server implementation.Findings
Both endpoints are fully in sync:
POST /luma/videos— all 11 parameters (loop,action,prompt,timeout,video_id,aspect_ratio,video_url,enhancement,callback_url,end_image_url,start_image_url) are correctly implemented across the four video tools.POST /luma/tasks—id,ids, andaction(enum:retrieve/retrieve_batch) are correctly implemented intask_tools.py.Re:
qualityparameterThe recent Docs commits included a test addition of
quality(fe255ba) immediately followed by a revert (9f0ded0). The parameter is absent from the current spec and was never present in the MCP code — no action required.