place_details — API Direct MCP Tool
place_details
(place details) is one of 102 tools on the
API Direct
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call place_details from your client
- Claude Code API Direct place_details run in your project directory
- Claude Desktop API Direct place_details ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor API Direct place_details ~/.cursor/mcp.json
- VS Code API Direct place_details .vscode/mcp.json
- Zed API Direct place_details ~/.config/zed/settings.json
- Windsurf API Direct place_details ~/.codeium/windsurf/mcp_config.json
- Cline API Direct place_details ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI API Direct place_details ~/.gemini/settings.json
- Grok API Direct place_details .mcp.json (in your project root)
- ChatGPT API Direct place_details Settings → Connectors → Advanced → Developer mode
- Claude.ai API Direct place_details Settings → Connectors → Add custom connector
- LangChain API Direct place_details pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http api-direct https://apidirect.io/mcpOther tools on this server
- list_skills
- get_skill
- search_linkedin
- linkedin_person_posts
- linkedin_post_details
- linkedin_company_details
- linkedin_company_posts
- search_linkedin_companies
- search_linkedin_jobs
- linkedin_job_details
- search_twitter
- search_twitter_users
- twitter_user_profile
- twitter_user_tweets
- twitter_user_followers
- twitter_user_following
- twitter_verified_followers
- twitter_user_replies
- twitter_tweet_details
- twitter_tweet_retweets
- twitter_tweet_quotes
- twitter_tweet_comments
- twitter_trends
- search_reddit
- search_reddit_comments
- search_reddit_users
- search_youtube
- search_youtube_channels
- get_youtube_comments
- youtube_channel_details
- youtube_video_details
- search_instagram
- search_instagram_users
- instagram_user_profile
- instagram_user_posts
- instagram_post_details
- instagram_user_followers
- instagram_user_following
- instagram_user_stories
- instagram_user_highlights
- instagram_highlight_stories
- instagram_post_comments
- instagram_comment_replies
- instagram_post_likes
- instagram_hashtag_posts
- search_threads
- search_threads_users
- threads_user_profile
- threads_user_posts
- truthsocial_user_posts
- search_bluesky
- search_bluesky_users
- bluesky_user_profile
- bluesky_user_posts
- bluesky_user_followers
- bluesky_user_following
- bluesky_user_likes
- bluesky_post_details
- bluesky_post_comments
- bluesky_post_likes
- bluesky_post_quotes
- bluesky_post_reposts
- search_tiktok
- search_tiktok_users
- tiktok_user_profile
- tiktok_video_details
- facebook_page_details
- facebook_page_posts
- facebook_page_photos
- facebook_page_videos
- facebook_page_reels
- facebook_page_reviews
- facebook_group_details
- facebook_group_posts
- facebook_post_comments
- search_facebook_posts
- search_facebook_pages
- search_facebook_videos
- search_facebook_events
- search_facebook_locations
- search_forums
- search_news
- search_web
- google_ai_mode
- search_places
- place_reviews
- place_photos
- search_amazon_products
- amazon_product_details
- amazon_seller_profile
- amazon_seller_reviews
- amazon_seller_products
- amazon_best_sellers
- trustpilot_company_reviews
- search_trustpilot_companies
- trustpilot_category_companies
- trustpilot_category_newest
- trustpilot_category_details
- search_trustpilot_categories
- trustpilot_user_profile
- batch_requests
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.