purge_image_cache — Gumlet MCP Tool
purge_image_cache
(purge image cache) is one of 95 tools on the
Gumlet
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call purge_image_cache from your client
- Claude Code Gumlet purge_image_cache run in your project directory
- Claude Desktop Gumlet purge_image_cache ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Gumlet purge_image_cache ~/.cursor/mcp.json
- VS Code Gumlet purge_image_cache .vscode/mcp.json
- Zed Gumlet purge_image_cache ~/.config/zed/settings.json
- Windsurf Gumlet purge_image_cache ~/.codeium/windsurf/mcp_config.json
- Cline Gumlet purge_image_cache ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Gumlet purge_image_cache ~/.gemini/settings.json
- Grok Gumlet purge_image_cache .mcp.json (in your project root)
- ChatGPT Gumlet purge_image_cache Settings → Connectors → Advanced → Developer mode
- Claude.ai Gumlet purge_image_cache Settings → Connectors → Add custom connector
- LangChain Gumlet purge_image_cache pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://mcp.gumlet.com/mcp/v1Other tools on this server
- insights_breakdown_data
- insights_aggregated_data
- list_sdks
- get_sdk
- import_from_vimeo
- create_asset
- create_asset_direct_upload
- get_asset_details
- delete_asset
- update_asset
- thumbnail_select
- thumbnail_upload
- upload_subtitles
- complete_subtitle_upload
- asset_audio_upload
- complete_audio_upload
- create_update_chapter
- retrieve_analytics
- top_assets
- retrieve_part_url
- complete_multipart_upload
- list_profiles
- create_profile
- get_profile
- update_profile
- delete_profile
- get_all_playlists
- create_playlist
- add_asset_playlist
- remove_asset_playlist
- update_playlist
- delete_playlist
- get_playlist_assets
- reorder_asset_playlist
- list_webhooks
- create_webhook
- update_webhook
- delete_webhook
- list_sources
- create_image_source
- get_image_sources_source_id
- update_image_source
- delete_source
- retrieve_image_analytics
- create_live_asset
- update_live_asset
- get_live_asset_status
- delete_live_asset
- complete_live_stream
- filter_live_assets
- recover
- start_live
- thumbnail_upload_live
- list_workspaces
- create_workspace
- get_workspace
- update_workspace
- delete_workspace
- list_folders
- create_folder
- get_folder
- update_folder
- delete_folder
- remove_assets_folder
- list_assets
- invite_channel_viewers
- remove_channel_viewers
- invite_channel_viewers_csv
- asset_status_history
- viewer_analytics_data
- analytics_breakdown_data
- analytics_aggregated_data
- image_purge
- fetch_org
- fetch_user
- fetch_audit_logs
- list_recycle_bin
- assets_delete_many
- assets_tag_many
- asset_analytics
- list_channel_subscribers
- webhook_history
- list_invoices
- fetch_billing_details
- update_billing_details
- fetch_upcoming_invoice
- list_live_workspaces
- live_workspace_create
- live_workspace_update
- live_workspace_delete
- live_usage_analytics
- global_search
- multipart_upload_abort
- multipart_upload_list
This list was read from the server itself, by connecting to it and calling tools/list on 11 November 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.