delete_brand_video — Siren MCP Tool Mutating
delete_brand_video
(delete brand video) 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 delete_brand_video from your client
- Claude Code Siren delete_brand_video run in your project directory
- Claude Desktop Siren delete_brand_video ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Siren delete_brand_video ~/.cursor/mcp.json
- VS Code Siren delete_brand_video .vscode/mcp.json
- Zed Siren delete_brand_video ~/.config/zed/settings.json
- Windsurf Siren delete_brand_video ~/.codeium/windsurf/mcp_config.json
- Cline Siren delete_brand_video ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Siren delete_brand_video ~/.gemini/settings.json
- Grok Siren delete_brand_video .mcp.json (in your project root)
- ChatGPT Siren delete_brand_video Settings → Connectors → Advanced → Developer mode
- Claude.ai Siren delete_brand_video Settings → Connectors → Add custom connector
- LangChain Siren delete_brand_video pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http siren https://mcp.mysiren.ai/mcp
Other 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
- list_brand_videos
- upload_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.