Plainly Videos MCP Server (Adobe After Effects Automation) AI Integration

Return all Projects and Designs the authenticated user can render. Designs are pre-made projects with variants available for all users. Projects are created and maintained by the user, and may have custom templates. Each item includes a lightweight preview of its templates/variants (name, aspect ratio, duration) plus a parent-level description and metadata (tags, category, attributes). Filtering guidance (semantic first): - First, determine relevance using: metadata.tags, metadata.category, metadata.attributes, description, and name. - Only after a semantic match, consider technical fit (aspectRatio, durationSeconds) to break ties. - Do not guess or list unrelated items. If nothing is relevant, respond: "No suitable templates found." Use when: - The user wants to browse, search, or choose a template/variant. - Before recommending or starting a render for a targeted campaign, platform, or audience. Follow-ups: - `get_renderable_item_details` — fetch the full parameter schema/defaults for the chosen template/variant before rendering.

Return the renderable templates/variants under a specific Project or Design, including the parameters required to render each. How to use: - Call this after the user selects a candidate from `list_renderable_items`. - For each returned template/variant: 1) Read its parameters. 2) Collect values for all parameters marked mandatory. 3) Respect the declared type (e.g., MEDIA (image) vs MEDIA (video)). Guidance: - Prefer `description` to understand the intent of each parameter; fall back to `label`, then `key` if needed. - If any mandatory parameter is missing or unclear, ask the user to provide it—do not guess. - If the parent has multiple templates/variants, choose the one that best matches the user's stated goals and constraints; otherwise present the options. Use when: - The user wants details/parameters for a chosen template/variant. - Immediately before preparing values and calling render_item. Follow-ups: - `render_item` — submit a render for the chosen template/variant with the collected parameter values.

Create a render for a selected Project template or Design variant with specified parameters. How to use: - Call this after the user selects a candidate from `get_renderable_items_details`. - Call this only once the user approved all parameters for the chosen template/variant. Guidance: - Never submit more than one render with the same parameters, unless the user explicitly requests it. - Use parameters to customize the render. - All mandatory parameters must be provided. - Provide values for optional parameters if it makes sense. - Parameter types must be respected: - STRING: text string relevant to the parameter context. - MEDIA: URL to a media file (image, audio, or video). Ensure the URL is publicly accessible and points directly to the media file. - MEDIA (image): URL to an image file (jpg, png, etc.). - MEDIA (audio): URL to an audio file (mp3, wav, etc.). - MEDIA (video): URL to a video file (mp4, mov, etc.). - COLOR: hex color code (e.g. FF5733). - If a parameter has a default value and the user does not provide a value, the default will be used. - If the user is unsure about a parameter, ask for clarification rather than guessing. - When referencing parameters in conversation, use their `label` or `description` for clarity. Use when: - The user wants to create a video from a specific template/variant with defined parameters.

Check the status of a render job. Available states: - PENDING: The render job has been created but not yet added to the queue. - THROTTLED: The render job is waiting due to rate limiting. It will be started as soon as a slot opens, no need for manual retries. - QUEUED: The render job is in the queue and will start soon. - IN_PROGRESS: The render job is currently being processed. - DONE: The render job has completed successfully. The output URL will be provided. - FAILED: The render job encountered an error and did not complete successfully. Error details will be provided. - INVALID: The render job was invalid (e.g., due to incorrect parameters). Error details will be provided. - CANCELLED: The render job was cancelled by the user. Response format: - Always include a link to the render details page. - If the render is still in progress (PENDING, THROTTLED, QUEUED, IN_PROGRESS) tell user to check the status again later. - If the render is DONE, return the output URL and the render page details. - If the render FAILED or is INVALID, return the error message and details. Use when: - You need to check the progress of a render job - You want to retrieve the final render output URL - You want to retrieve render error details if the job failed