get_v2_search — instagram MCP Tool Read-only
get_v2_search
(get v2 search) is one of 22 tools on the
instagram
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_v2_search from your client
- Claude Code instagram get_v2_search run in your project directory
- Claude Desktop instagram get_v2_search ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor instagram get_v2_search ~/.cursor/mcp.json
- VS Code instagram get_v2_search .vscode/mcp.json
- Zed instagram get_v2_search ~/.config/zed/settings.json
- Windsurf instagram get_v2_search ~/.codeium/windsurf/mcp_config.json
- Cline instagram get_v2_search ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI instagram get_v2_search ~/.gemini/settings.json
- Grok instagram get_v2_search .mcp.json (in your project root)
- ChatGPT instagram get_v2_search Settings → Connectors → Advanced → Developer mode
- Claude.ai instagram get_v2_search Settings → Connectors → Add custom connector
- LangChain instagram get_v2_search pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http instagram https://mcp.jojapi.com/instagramOther tools on this server
- get_user_details_by_username
- get_user_posts_by_username
- get_user_stories_by_username
- get_v3_user_details_by_username
- get_v3_user_stories
- get_v3_1_user_details_by_username
- get_v3_user_details_by_id
- get_v4_highlight_stories
- get_v2_post_details_by_shortcode
- get_v2_user_following_hashtags
- get_v2_user_tagged_posts
- get_v2_user_posts
- get_v4_user_highlights
- get_v4_user_stories
- get_v4_1_user_posts
- get_v4_user_posts
- get_v4_user_details_by_username
- get_v2_user_details_by_id
- get_v2_user_details_by_username
- get_v2_location_posts
- get_v2_tag_posts
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.