linkedin-relay-mcp 3.0.1 → 3.0.3
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.
- package/.claude/skills/linkedin-relay/SKILL.md +23 -8
- package/dist/cli.js +4 -2
- package/dist/cli.js.map +1 -1
- package/package.json +1 -1
|
@@ -183,14 +183,29 @@ call again.
|
|
|
183
183
|
|
|
184
184
|
## What this tool will not do
|
|
185
185
|
|
|
186
|
-
Writes
|
|
187
|
-
|
|
188
|
-
|
|
189
|
-
|
|
190
|
-
|
|
191
|
-
`
|
|
192
|
-
|
|
193
|
-
|
|
186
|
+
Writes are **not on this surface at all**. They exist only as CLI commands the user runs themselves:
|
|
187
|
+
|
|
188
|
+
| command | does |
|
|
189
|
+
|---|---|
|
|
190
|
+
| `lnrelay share "<text>"` | post to their own feed |
|
|
191
|
+
| `lnrelay comment <activity-urn> "<text>"` | comment on a post |
|
|
192
|
+
| `lnrelay reply <comment-urn> "<text>"` | reply, nested under that comment |
|
|
193
|
+
| `lnrelay edit <comment-urn> "<text>"` | change the text of their own comment |
|
|
194
|
+
| `lnrelay react <urn> [--type X] [--remove]` | react to a post or comment |
|
|
195
|
+
| `lnrelay delete <activity-urn \| comment-urn>` | delete their post or comment |
|
|
196
|
+
|
|
197
|
+
The urn decides nothing on its own — `comment`, `reply` and `edit` are separate verbs because they
|
|
198
|
+
are separate operations, and passing a comment urn to `comment` is refused rather than guessed at.
|
|
199
|
+
|
|
200
|
+
Each stops at an interactive terminal, shows exactly what it will send and over which surface, and
|
|
201
|
+
requires the user to type a token derived from the content.
|
|
202
|
+
|
|
203
|
+
Two things worth telling a user who asks:
|
|
204
|
+
|
|
205
|
+
- `share` prefers LinkedIn's official OAuth scope and falls back to the private API when they have no
|
|
206
|
+
developer app — the prompt names which, and a Voyager write states the ToS breach. Why an app is
|
|
207
|
+
needed at all: `docs/DECISION-writes.md`.
|
|
208
|
+
- **Deleting a comment also deletes every reply under it**, including other people's. Verified live.
|
|
194
209
|
|
|
195
210
|
**Without a terminal there is no write and no network call.** That is deliberate and there is no
|
|
196
211
|
flag that changes it: a flag an agent could set would not be confirming anything. If the user asks
|
package/dist/cli.js
CHANGED
|
@@ -2182,7 +2182,8 @@ async function deleteComment(ref, urn, now, deps) {
|
|
|
2182
2182
|
action: "delete your comment",
|
|
2183
2183
|
payload: { urn },
|
|
2184
2184
|
summary: [`comment ${urn}`, `on post urn:li:activity:${ref.activityId}`],
|
|
2185
|
-
|
|
2185
|
+
// Verified live: deleting a parent took its three nested replies with it.
|
|
2186
|
+
reversibility: "NONE. A deleted comment is gone \u2014 AND SO IS EVERY REPLY UNDER IT, including other people's. Verified live.",
|
|
2186
2187
|
transport: "voyager"
|
|
2187
2188
|
};
|
|
2188
2189
|
const gated = await gateWrite("delete", plan, now, deps, { commitSpend: false });
|
|
@@ -3535,7 +3536,8 @@ async function replyToComment(confirmed, client) {
|
|
|
3535
3536
|
});
|
|
3536
3537
|
if (!result.ok) {
|
|
3537
3538
|
const out = { ok: false, code: result.code, message: result.message };
|
|
3538
|
-
|
|
3539
|
+
out.hint = /5\d\d|unexpected status/.test(result.message) ? "DO NOT RETRY BLINDLY. This endpoint has been observed returning 5xx after the reply was already created. Check the thread on LinkedIn before sending again." : result.hint ?? "";
|
|
3540
|
+
if (out.hint === "") delete out.hint;
|
|
3539
3541
|
return out;
|
|
3540
3542
|
}
|
|
3541
3543
|
return { ok: true, parent: parentThreadUrn(ref) };
|