set_cost_floor — amazon product research mcp MCP Tool Mutating
set_cost_floor
(set cost floor) is one of 82 tools on the
amazon product research mcp
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call set_cost_floor from your client
- Claude Code amazon product research mcp set_cost_floor run in your project directory
- Claude Desktop amazon product research mcp set_cost_floor ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor amazon product research mcp set_cost_floor ~/.cursor/mcp.json
- VS Code amazon product research mcp set_cost_floor .vscode/mcp.json
- Zed amazon product research mcp set_cost_floor ~/.config/zed/settings.json
- Windsurf amazon product research mcp set_cost_floor ~/.codeium/windsurf/mcp_config.json
- Cline amazon product research mcp set_cost_floor ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI amazon product research mcp set_cost_floor ~/.gemini/settings.json
- Grok amazon product research mcp set_cost_floor .mcp.json (in your project root)
- ChatGPT amazon product research mcp set_cost_floor Settings → Connectors → Advanced → Developer mode
- Claude.ai amazon product research mcp set_cost_floor Settings → Connectors → Add custom connector
- LangChain amazon product research mcp set_cost_floor pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http amazon-product-research-mcp https://app.webotee.com/mcpOther tools on this server
- lookup_product_by_barcode
- asin_bsr_history
- amazon_search_results
- evaluate_asin_sourcing
- evaluate_brand
- competitive_landscape
- risk_assessment
- xmkt_pricing_compare
- gating_repricing_advice
- find_brands_with_high_seller_churn
- categories_amazon_retreating
- top_velocity_brands
- top_sourcing_picks
- top_expanding_operators
- brands_gaining_sellers
- operator_brands_by_competition
- find_undercompeted_brands
- operator_compare
- brand_buybox_trajectory
- category_undercompeted_brands
- unauthorized_sellers
- operator_new_brands
- operator_lost_brands
- operator_category_dominance
- find_single_seller_brands
- operator_xmarket_presence
- brand_xmarket
- find_new_operators
- find_deconcentrating_brands
- brand_under_attack
- operator_top_asins
- operator_top_brands
- brand_similar
- brand_new_asins
- category_top_growers
- category_new_entrants
- category_metrics
- evaluate_category_for_private_label
- find_underserved_niches
- asin_comparables
- asin_buybox_history
- asin_profit_calc
- watchlist_delta
- watchlist_add_rule
- watchlist_stats
- watchlist_webwide
- map_violations_today
- filter_operators_by_fba_share
- filter_brands_by_fba_share
- brands_in_operator_network
- search_products
- shopping_search
- collect_asin_now
- watchlist_add
- watchlist_remove
- watchlist_list
- watchlist_diff
- operator_resells_what
- operator_concentration
- operator_new_on_brand
- operator_classifier
- playbook_create
- playbook_list
- playbook_run_now
- playbook_schedule
- find_product_across_web
- webotee_job_status
- authorized_seller_set
- authorized_seller_list
- buybox_loss_alert
- web_search
- alibaba_supplier_search
- find_sourcing_opportunities
- operator_buybox_losses
- my_products
- my_store
- my_competitors
- my_opportunities
- product_page_content
- keyword_demand
- keyword_cross_marketplace
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.