Enrich person recommendations
Recommendations on the target profile: who vouches for them and in what words. direction picks received (the default, what LinkedIn opens on) or given; these are two SEPARATE reads of the same screen, so asking for both spends the method twice. 2 credits, cached 7d. The counterpart carries a nickname, name, headline and network distance but NO ln_id: LinkedIn does not put the member urn in this payload, so enrich the nickname separately if you need the urn. created_at is parsed out of the free-text context line and is null when that line has no date. Needs BOTH the vanity slug and the member urn: pass profile_id AND public_identifier together to skip the resolve round trip.
Contract:
- MCP tool
enrich_linkedin_person_recommendations, registry packagemcp.linkedin/linkedin_enrichment, mountlinkedin.enrichment. - Operation
action, response envelopeaction. - Flags: creditable: the response carries a
creditsblock and the call can debit the team ledger.
Authorizations
Access token issued by gtm.service.id. Its access_identity claim carries team_sid, actor_sid and actor_type, and that team scope is authoritative.
Team scope for tokens that do not carry one. Ignored when the token already names a team.
Body
Request body of enrich_linkedin_person_recommendations.
ln_id (ACoAA…) or sn_id (ACwAA…), interchangeable for dispatch. Provide profile_id XOR public_identifier.
128Vanity slug from /in/…. Provide public_identifier XOR profile_id. On sub-record methods a slug-only call needs a stored URN (run person-lite-profile first) or is refused not_dispatchable.
100received (default) = written ABOUT the target; given = written BY the target. Separate reads, so each spends the method.
received, given Preferred executor account (ln_ac_…). OPTIONAL: given + enrichment bucket budget → own account, charged 0; given + bucket saturated → pool + credits; omitted → pool + credits. There is no use_credit flag: §9.5 resolution is automatic.
18^ln_ac_Replay guard (team_sid, idempotency_key). A repeat with the same key returns the stored ledger outcome: no re-execution, no double charge.
128