list_brand_videos — Siren MCP Tool Read-only
list_brand_videos
(list brand videos) is one of 36 tools on the
Siren
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call list_brand_videos from your client
- Claude Code Siren list_brand_videos run in your project directory
- Claude Desktop Siren list_brand_videos ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Siren list_brand_videos ~/.cursor/mcp.json
- VS Code Siren list_brand_videos .vscode/mcp.json
- Zed Siren list_brand_videos ~/.config/zed/settings.json
- Windsurf Siren list_brand_videos ~/.codeium/windsurf/mcp_config.json
- Cline Siren list_brand_videos ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Siren list_brand_videos ~/.gemini/settings.json
- Grok Siren list_brand_videos .mcp.json (in your project root)
- ChatGPT Siren list_brand_videos Settings → Connectors → Advanced → Developer mode
- Claude.ai Siren list_brand_videos Settings → Connectors → Add custom connector
- LangChain Siren list_brand_videos pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http siren https://mcp.mysiren.ai/mcpOther tools on this server
- get_account
- list_runs
- get_run
- create_campaign
- list_films
- describe_film
- clarify_brief
- render_asset
- upload_media
- post_run
- schedule_post
- get_brand_dna
- update_brand_dna
- list_product_screens
- upload_product_screen
- update_product_screen
- delete_product_screen
- upload_logo
- get_mascot
- create_mascot
- mascot_step
- list_people
- add_person
- delete_person
- list_media
- get_performance
- list_posts
- buy_credits
- upload_brand_video
- delete_brand_video
- delete_media
- studio_templates
- studio_card
- studio_automate
- studio_schedule
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.