get_ad_fatigue — Run1Ads: live Meta ads consultant MCP Tool Read-only
get_ad_fatigue
(get ad fatigue) is one of 15 tools on the
Run1Ads: live Meta ads consultant
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_ad_fatigue from your client
- Claude Code Run1Ads: live Meta ads consultant get_ad_fatigue run in your project directory
- Claude Desktop Run1Ads: live Meta ads consultant get_ad_fatigue ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Run1Ads: live Meta ads consultant get_ad_fatigue ~/.cursor/mcp.json
- VS Code Run1Ads: live Meta ads consultant get_ad_fatigue .vscode/mcp.json
- Zed Run1Ads: live Meta ads consultant get_ad_fatigue ~/.config/zed/settings.json
- Windsurf Run1Ads: live Meta ads consultant get_ad_fatigue ~/.codeium/windsurf/mcp_config.json
- Cline Run1Ads: live Meta ads consultant get_ad_fatigue ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Run1Ads: live Meta ads consultant get_ad_fatigue ~/.gemini/settings.json
- Grok Run1Ads: live Meta ads consultant get_ad_fatigue .mcp.json (in your project root)
- ChatGPT Run1Ads: live Meta ads consultant get_ad_fatigue Settings → Connectors → Advanced → Developer mode
- Claude.ai Run1Ads: live Meta ads consultant get_ad_fatigue Settings → Connectors → Add custom connector
- LangChain Run1Ads: live Meta ads consultant get_ad_fatigue pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http consultant https://run1ads.ai/mcp/rpcOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 20 October 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.