GTM API / Set my position

Add, edit or remove ONE position (work experience entry) on the connected account's OWN LinkedIn profile. No position_id = add (title, company_name and start_date required, end_date unless is_current). position_id = edit: send only the fields that change, the backend reads the position's form first and submits it whole (the LinkedIn wire replaces the form); is_current: true drops the end date, an end_date ends a current position. position_id + delete: true = remove it (the backend reads the form and mirrors it into the delete, as LinkedIn's own editor does). position_id is the numeric id each entry carries on the account's own experience list (enrich_linkedin_person_experience on its own profile, or the add's answer). Company, geo and employment-type ids are LinkedIn's own numeric ids; without them the company is free text and the location display text only. Spends one edit_profile slot per call. Contract: - MCP tool set_linkedin_account_my_position, registry package mcp.linkedin/linkedin_accounts, mount linkedin.accounts. - Operation action, response envelope action. - Flags: dangerous: the MCP layer gates it behind a preview/commit token, and the effect cannot be undone through this API; paced: a call spends the edit_profile smart-limit bucket of the account it runs on, and calls of one bucket are spaced per account. A short wait is slept by the server; a longer one answers 429 rate_limited with context.retry_after, and the same call succeeds from that moment. Parallel calls on one account queue behind each other.