Enrich post details (not shipped)
⛔ NOT SHIPPED YET. Contract locked, capability not built; returns not_implemented, do not retry. One post’s own data: full text, author, media, engagement counters, per-reaction breakdown. Accepts activity_urn XOR url (a URL is resolved to the URN backend-side). 2 credits, cached 7d. WHO engaged is scraping (get-post-commenters / get-post-reactors / get-post-resharers).
Not shipped yet. The registry marks this route availability=stub_501: the backend validates the whole request and then answers 501 not_implemented. The request contract is final, so integrations can be written and tested against it today. Marked deprecated so generated clients flag it at compile time; this is a NOT-YET flag, not a sunset.
Contract:
- MCP tool
enrich_linkedin_post_details, 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_post_details.
urn:li:activity:… . Provide activity_urn XOR url.
Any post URL/shortlink; resolved to the URN backend-side. Provide url XOR activity_urn.
2048Preferred 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