linkedinlisted

# LinkedIn -- Best Practices Reference This is the canonical reference for how the Exobrain interacts with LinkedIn via the `linkedin-scraper-mcp` server. All skills that touch LinkedIn MUST follow these conventions. ## CRITICAL -- Read-Only Rule **The LinkedIn MCP is READ-ONLY for Alex.** This is a hard rule, not a default. The cost of getting his account flagged or banned is much higher than any convenience gained from automated writes. - **Allowed**: search and lookup tools (`search_*`, `get_*`) - **Forbidden**: any action that creates content, sends messages, or modifies Alex's network - **If Alex needs to send a message or connection request**: draft it for him as text, and tell him to send it manually from the LinkedIn UI. Never invoke a write tool, even if Alex asks -- confirm explicitly that he wants it manual, then hand off the draft. | Status | Tools | |--------|-------| | ✅ ALLOWED | `get_my_profile`, `get_person_profile`, `search_people`, `get_sidebar_profiles`, `search_companies`, `get_company_profile`, `get_company_employees`, `get_company_posts`, `search_jobs`, `get_job_details`, `get_feed`, `get_inbox`, `get_conversation`, `search_conversations`, `close_session` | | ❌ FORBIDDEN | `send_message`, `connect_with_person`, and any future like/comment/post/react/follow/endorse tools | The inbox and conversation read tools are allowed (Alex can see his own messages), but never reply or send through them. ## Bot-Detection Avoidance The `linkedin-scraper-mcp` s