No user-submitted related servers found.
Scored across 23 tools
Most tools target a distinct resource+action and descriptions clarify boundaries (e.g. get_asset vs get_asset_by_render_id). Some grouping is dense — ingest_source, transfer_asset, and create_upload_url_file all concern getting files in, and render vs render_template vs generate_asset require reading descriptions to distinguish. Still, each has a clearly stated purpose an agent can match to.
Predominantly consistent verb_noun snake_case (get_render, list_templates, create_template, delete_source). Minor deviations: 'render' lacks a noun object, and 'probe_media' uses a less common verb, but nothing is ambiguous or chaotically mixed.
23 tools span three logical sub-APIs (edit, serve, ingest) plus asset generation, so the count is high but largely earned. Slightly on the heavy side, with some read/write pairs that could arguably be consolidated, but nothing feels redundant.
Templates have full CRUD, sources and assets have get/list/create/delete, and rendering plus generation are covered with status polling. Minor gaps exist: no cancel-render, no list-renders, and serve assets have no list endpoint, but core workflows are workable.