Skip to main content
Glama

Related Servers

Alternatives to no-api-media-mcp

No user-submitted related servers found.

    Related Servers

    TDQS

    A3.5/5.0

    Scored across 25 tools

    Disambiguation4/5

    Most tools occupy a distinct lifecycle slot (brief → generate → audit → compose → deliver → optimize), and descriptions explicitly route between look-alikes such as video_quote vs video_generate and design_brief vs project_profile. The main soft overlaps are social_sizes vs deliver (multi-preset vs single-platform pipeline) and media_optimize vs deliver's built-in compression, which an agent must read carefully to choose correctly.

    Naming Consistency3/5

    Tools mix verb_noun (design_brief, composition_check, media_cleanup) with noun_verb (image_generate, video_generate, palette_extract, background_remove), bare nouns (brand_profiles, accounts_status, usage_report), and lone verbs (compose, deliver). Each name is readable in isolation, but there is no single predictable pattern an agent can rely on.

    Tool Count3/5

    Twenty-five tools is at the heavy boundary for a media pipeline; nearly all serve a real stage (generation, quoting, editing, optimization, delivery, cleanup, accounts), but the surface is broad enough that an agent must scan a lot to find a step. A few (usage_report, loop_check) are niche enough to consider folding in.

    Completeness4/5

    The generate → check → compose → deliver → optimize → clean lifecycle is well covered, including cost quoting, brand profiles, and local editing via video_edit. Gaps are minor: image editing is limited to background_remove/social_sizes/deliver, with no general crop/resize/retouch for stills analogous to video_edit.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing