linkedin

これはレビュー時に保存された抜粋です。完全で最新の内容は外部ソースを確認してください。

---
name: linkedin
description: When a workflow needs public LinkedIn data through UnifAPI — company pages, follower/employee counts, open jobs and job-count, member insights, people, posts, or engagement. Also use on "research this company on LinkedIn," "who works at," "open roles at," "LinkedIn profile for," "company posts," or when another skill (account research, news signal, buying signal, competitor profiling) needs the deterministic LinkedIn read path. Connect via the `unifapi` skill first. Read-only research, never connects or messages.
license: MIT
metadata:
  author: UnifAPI
  version: "1.0.0"
  homepage: https://unifapi.com/agents/linkedin
  source: https://github.com/unifapi-agent/agents
---

# linkedin

The deterministic read path for public **LinkedIn** data through UnifAPI. This is
a **Data Skill**: it does not run a marketing job on its own — it names the
concrete `linkedin/...` operations, response shapes, and gotchas so any
B2B-first workflow (account research, news signals, buying signals, competitor
profiling) reads from one known recipe instead of rediscovering the surface each
time.

Read-only — **eyes, not hands**. It researches public LinkedIn data and returns
cited records; it never connects, messages, or applies, and UnifAPI never holds
LinkedIn credentials.

## Use the `unifapi` skill for live evidence

Connect once through the shared **`unifapi`** skill (OAuth MCP), then call the
operations below. Companies are keyed by their public **`{slug}`** (the vanity
segment of the company URL) and people by their public **`{username}`** — read
both from the LinkedIn URL, not a numeric id. Keep any `billing` metadata so the
output can state record cost.

## Response contract

Single-entity endpoints return the object in `data`:

```json
{
  "request_id": "unif_...",
  "data": {},
  "billing": { "records_charged": 1, "balance_remaining": 99 }
}
```

List endpoints return an array in `data` plus `pagination`:

```json
{
  "request_id": "unif_...",
  "data": [],
  "pagination": { "has_more": false, "next_cursor": null },
  "billing": { "records_charged": 1 }
}
```

When `pagination.has_more` is true, pass `pagination.next_cursor` as the next
request's `cursor`. Always preserve `billing` when reporting cost.

## Core operations

| Need                         | Operation                                                       |
| ---------------------------- | --------------------------------------------------------------- |
| Company page                 | `linkedin/companies/{slug}`                                     |
| Company headcount signal     | `linkedin/companies/{slug}/job-count` · `.../jobs`              |
| Company people               | `linkedin/companies/{slug}/people`                              |
| Member insights              | `linkedin/companies/{slug}/member-insights`                     |
| Company posts                | `linkedin/companies/{slug}/posts`                               |
| Person profile               | `linkedin/users/{username}` · `.../about` · `.../experience`    |
| Person reach                 | `linkedin/users/{username}/follower-count`                      |
| Person posts / reactions     | `linkedin/users/{username}/posts` · `.../reactions`             |
| Search people                | `linkedin/search/people` (`?title=&current_company=&industry=`) |
| Search jobs / posts          | `linkedin/search/jobs` · `linkedin/search/posts`                |
| Job / post by id             | `linkedin/jobs/{id}` · `linkedin/posts/{id}` (`.../comments`)   |
| Resolve a geocode / industry | `linkedin/search/locations` · `linkedin/search/industries`      |

Need a field not listed here? Use the `unifapi` skill's `get_operation` to read
the exact schema before calling — but pick the operation from this table, don't
discover blind.

## Workflow

The deterministic recipes. Pick the one that matches the job; each names exactly
what to call.

1. **Resolve an account.** Take the company