linkedin-relay-mcp 3.10.0 → 3.10.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -12,7 +12,8 @@ in the request path.
12
12
  ## Three things to know before you call anything
13
13
 
14
14
  1. **Every call spends a budget that cannot be topped up.** Caps are deliberately low (30 profile
15
- reads a day, 25 searches, 250 requests total) because LinkedIn restricts accounts for *read*
15
+ reads a day, 25 searches, 350 requests total; job hunting has its own 150 job searches and 60
16
+ job reads) because LinkedIn restricts accounts for *read*
16
17
  velocity alone — several documented restrictions involved no automation and no writes, just fast
17
18
  browsing. Check `meta.budget.remaining`; when it's low, tell the user and stop rather than
18
19
  spending the rest.
@@ -58,7 +59,7 @@ Out-of-network people come back as `name: "LinkedIn Member"` with a `/headless`
58
59
  LinkedIn behaviour, not a bug — LinkedIn will not name them to this account. Say so rather than
59
60
  presenting it as a data problem.
60
61
 
61
- ### `jobs` — 1 search call per 25 results. Job search with every filter.
62
+ ### `jobs` — 1 job-search call per 25 results. Job search with every filter.
62
63
  ```
63
64
  jobs keywords:"<terms>" [location:"<place>" | geoId:"<id>"] [distance:<miles>]
64
65
  [posted:"24h|week|month|<N>h|<N>d"] [experience:[internship|entry|associate|mid-senior|director|executive]]
@@ -71,17 +72,18 @@ Each item: `id`, `title`, `company`, `location`, `workplace`, `listed` (YYYY-MM-
71
72
  `promoted`, `salary` (when the card shows one), `insights`, `url`. `compact` gives one line per job.
72
73
 
73
74
  - **Rank on the rows, then read the finalists with `job`.** `details` reads *every* row (1 profile
74
- call each, 30 a day) to add the apply link, applicants and employment type.
75
+ job read each, 60 a day) to add the apply link, applicants and employment type.
75
76
  - **Check `data.location`.** A typed location is resolved by LinkedIn, and the place it chose is
76
77
  reported there. "Vienna, Austria" resolved to one district of Vienna. Pass `geoId` for an exact
77
78
  place; ids are in `job_filters` under `populatedPlace`.
78
79
  - **Paging:** `meta.claimedCount` is LinkedIn's total, `meta.next` is the `start` for the next
79
80
  batch, and `meta.state` is `complete` only when the results ran out. LinkedIn serves at most 1000
80
81
  per search; narrow the query rather than paging deep.
81
- - For several searches (keyword variants), keep each one narrow with filters. Every 25 rows costs a
82
- search call, and the day has 25.
82
+ - Job hunting has its own budget: 150 job-search calls and 60 job reads a day, apart from the
83
+ people and company `search`. That is about ten keyword searches read in full. The same job turns
84
+ up under several keywords; merge the lists by `id` before reading any in full.
83
85
 
84
- ### `job` — 1 profile call. One job, in full.
86
+ ### `job` — 1 job read. One job, in full.
85
87
  ```
86
88
  job job:"<id | /jobs/view/ URL | ?currentJobId= URL>"
87
89
  ```
@@ -91,7 +93,7 @@ job job:"<id | /jobs/view/ URL | ?currentJobId= URL>"
91
93
  system), and `applied` / `saved` for this user. For an external application, `apply.url` goes to
92
94
  the employer's own site.
93
95
 
94
- ### `job-filters` — 1 search call. The knobs, with ids.
96
+ ### `job-filters` — 1 job-search call. The knobs, with ids.
95
97
  ```
96
98
  job_filters keywords:"<terms>" [location | geoId] [any jobs filter]
97
99
  ```
package/dist/cli.js CHANGED
@@ -946,6 +946,21 @@ var CAPS = {
946
946
  },
947
947
  search: { perDay: 25, provenance: "guessed", note: "no corroborated figure exists" },
948
948
  page: { perDay: 60, provenance: "guessed", note: "thread/feed pagination" },
949
+ // Set on 2026-10-14 by the owner's decision, for job hunting: about ten
950
+ // keyword searches read in full (25 jobs a page, often 100-300 a search),
951
+ // then the finalists read for their apply links. Kept apart from `search`
952
+ // so a hunt neither uses up nor is stopped by people and company research.
953
+ // Guesses like every other cap; the client's 3-15s gap still paces each call.
954
+ jobSearch: {
955
+ perDay: 150,
956
+ provenance: "guessed",
957
+ note: "job search pages and filter lists; set for ~10 keyword searches a day"
958
+ },
959
+ jobRead: {
960
+ perDay: 60,
961
+ provenance: "guessed",
962
+ note: "one job read in full, for its apply link"
963
+ },
949
964
  write: {
950
965
  // Raised from 10 on 2026-08-14 by the owner's explicit decision, after 10
951
966
  // blocked ordinary development on a tool whose writes are the point — a
@@ -961,7 +976,9 @@ var CAPS = {
961
976
  provenance: "guessed",
962
977
  note: "raised from 10 for development; still below the ~20/day connection lore per action type"
963
978
  },
964
- global: { perDay: 250, provenance: "guessed", note: "all classes combined" }
979
+ // Raised from 250 with the job classes, so a full hunt (~120 searches and
980
+ // 60 reads) still leaves room for everything else.
981
+ global: { perDay: 350, provenance: "guessed", note: "all classes combined" }
965
982
  };
966
983
  var MIN_GAP_MS = 3e3;
967
984
  function emptyLedger() {
@@ -3258,7 +3275,7 @@ function queryOf(req, filters) {
3258
3275
  async function collect(get, query, first, want) {
3259
3276
  const out = { jobs: [], exhausted: false, unknownTypes: {} };
3260
3277
  for (let start = first; out.jobs.length < want && start < MAX_RESULTS; start += PAGE_SIZE2) {
3261
- const res = await get(jobSearchUrl({ ...query, start, count: PAGE_SIZE2 }), "search");
3278
+ const res = await get(jobSearchUrl({ ...query, start, count: PAGE_SIZE2 }), "jobSearch");
3262
3279
  const page = res.ok ? parseJobCards(res.json) : res;
3263
3280
  if (!page.ok) {
3264
3281
  if (out.jobs.length === 0) return page;
@@ -3280,7 +3297,7 @@ async function collect(get, query, first, want) {
3280
3297
  }
3281
3298
  async function addDetails(get, jobs, withDescription) {
3282
3299
  for (const job of jobs) {
3283
- const res = await get(jobDetailUrl(job.id), "profile");
3300
+ const res = await get(jobDetailUrl(job.id), "jobRead");
3284
3301
  const detail = res.ok ? parseJobDetail(res.json) : res;
3285
3302
  if (!detail.ok) return detail.code;
3286
3303
  const { description, id: _id, url: _url, ...rest } = detail.job;
@@ -3336,7 +3353,7 @@ async function runJob(input, opts = {}, fetch2) {
3336
3353
  }
3337
3354
  const get = fetch2 ?? liveFetch("job", opts.quiet === true);
3338
3355
  if (typeof get !== "function") return get;
3339
- const res = await get(jobDetailUrl(id), "profile");
3356
+ const res = await get(jobDetailUrl(id), "jobRead");
3340
3357
  if (!res.ok) return err("job", res.code, res.message, res.hint);
3341
3358
  const detail = parseJobDetail(res.json);
3342
3359
  if (!detail.ok) return err("job", detail.code, detail.message, detail.hint);
@@ -3348,7 +3365,7 @@ async function runJobFilters(req, opts = {}, fetch2) {
3348
3365
  const get = fetch2 ?? liveFetch("job-filters", opts.quiet === true);
3349
3366
  if (typeof get !== "function") return get;
3350
3367
  const url = jobFiltersUrl({ ...queryOf(req, selection2.filters), start: 0, count: PAGE_SIZE2 });
3351
- const res = await get(url, "search");
3368
+ const res = await get(url, "jobSearch");
3352
3369
  const parsed = res.ok ? parseJobFilters(res.json) : res;
3353
3370
  if (!parsed.ok) return err("job-filters", parsed.code, parsed.message, parsed.hint);
3354
3371
  return ok("job-filters", {
@@ -3597,7 +3614,15 @@ function runBudget(now, resetCooldown, confirmed) {
3597
3614
  `moved to ${corrupt.quarantinedTo}. A corrupt ledger is NOT treated as an empty one \u2014 that would silently restore a full budget. Inspect it, then re-run.`
3598
3615
  );
3599
3616
  }
3600
- const classes = ["profile", "search", "page", "write", "global"];
3617
+ const classes = [
3618
+ "profile",
3619
+ "search",
3620
+ "page",
3621
+ "jobSearch",
3622
+ "jobRead",
3623
+ "write",
3624
+ "global"
3625
+ ];
3601
3626
  const { value: cooldown } = loadCooldown();
3602
3627
  return ok("budget", {
3603
3628
  classes: classes.map((c) => ({
@@ -4024,7 +4049,7 @@ var COMMANDS = [
4024
4049
  },
4025
4050
  {
4026
4051
  name: "jobs",
4027
- cost: "1 search call per 25 jobs; --details adds 1 profile call per job",
4052
+ cost: "1 job-search call per 25 jobs; --details adds 1 job read per job",
4028
4053
  summary: "Job search with every filter the jobs page has. Cards carry id, title, company, place, workplace, listed date, Easy Apply. Read finalists with `job`.",
4029
4054
  usage: 'lnrelay jobs "<keywords>" [--location "<place>" | --geo <id>] [--distance <miles>]\n [--posted 24h|week|month|<N>h|<N>d] [--experience internship,entry,associate,\n mid-senior,director,executive] [--type full-time,part-time,contract,temporary,\n volunteer,internship,other] [--workplace on-site,remote,hybrid] [--easy-apply]\n [--under-10] [--verified] [--in-network] [--fair-chance] [--company <ids>]\n [--industry <ids>] [--function <codes>] [--title <ids>] [--place <geo-ids>]\n [--filter key=v1,v2 ...] [--sort recent|relevant] [--limit N] [--start N]\n [--details [--description]] [--compact | --fields a,b,c]\n Ids for --company/--industry/--title/--place/--filter come from `job-filters`.\n The resolved place is in data.location: check it, "Vienna" may resolve narrow.',
4030
4055
  audience: ["cli", "mcp"],
@@ -4033,7 +4058,7 @@ var COMMANDS = [
4033
4058
  },
4034
4059
  {
4035
4060
  name: "job",
4036
- cost: "1 profile call",
4061
+ cost: "1 job read",
4037
4062
  summary: "One job: description, apply link (external or Easy Apply), applicants, state.",
4038
4063
  usage: "lnrelay job <id|job-url>",
4039
4064
  audience: ["cli", "mcp"],
@@ -4042,7 +4067,7 @@ var COMMANDS = [
4042
4067
  },
4043
4068
  {
4044
4069
  name: "job-filters",
4045
- cost: "1 search call",
4070
+ cost: "1 job-search call",
4046
4071
  summary: "Every job filter for a query, with option ids and live counts: what `jobs --filter` and --company/--industry/--title/--place take.",
4047
4072
  usage: 'lnrelay job-filters "<keywords>" [--location "<place>" | --geo <id>] [jobs filters]',
4048
4073
  audience: ["cli", "mcp"],