linkedin-post-analytics

Gate (run first)

1. Pattern: CONNECTORS.md three-step for this integration: Discover — no standard LinkedIn MCP here; Configure — user logged into LinkedIn in the host browser (they sign in); Browser access — ask Claude in Chrome and/or computer use (neither / one / both). If neither or no tooling, stop—do not scrape without read-only approval for the chosen mode(s).
2. {user_dir}: Resolve the job-search folder; networking data is {user_dir}/CareerNavigator/networking.json.
3. Scheduled unattended runs: If this invocation came from /schedule (or user asked for unattended), do not ask interactive browser/tooling questions. Continue only when prior consent is already saved in {user_dir}/CareerNavigator/profile.md under ## LinkedIn:
   • LinkedIn slug: <value>
   • LinkedIn analytics permission: granted
   • LinkedIn analytics mode: chrome | computer | either If any of these are missing, stop with a concise setup message telling the user to run one interactive setup once.

Tool-call guidance

Preferred order: for interactive runs, use the user-approved mode (chrome, computer, or either). If mode is either, try Claude in Chrome first, then computer.

Claude in Chrome path (strict, typed params):

• First try tabs_context_mcp with correctly typed values (for example, createIfEmpty must be the boolean true, not the string "true").
• If context initialization still fails, call tabs_create_mcp, then retry tabs_context_mcp once.
• Then call navigate to the LinkedIn URL.
• If navigate fails because tabId is typed incorrectly, retry once with a numeric tabId (integer, not quoted).
• If still failing, stop with: "Claude in Chrome couldn't initialize a valid tab context. Open Chrome, confirm you're signed into LinkedIn, and rerun linkedin-post-analytics."

No circular fallback loops:

• At most one retry per failing step.
• Do not bounce between tools repeatedly.
• If chosen mode fails, only try the alternate mode when the saved/approved mode is either.