Skip to main content
Glama

Mark a connection

connections_mark

Records your keep, remove, or outcome decision for a LinkedIn connection so cleanup decisions are tracked, without deleting anything on LinkedIn; a warning also writes a halt file that stops further actions.

Instructions

Records the owner's decision for one connection: keep or remove overrides the rating; removed or skipped records what happened when a person removed it or passed it by in LinkedIn; warning records a LinkedIn warning and writes the halt file named by LINKEN_HALT_FILE, which stops connections_next, post_publish, comment_create and reply_open. It removes nothing on LinkedIn.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>",
      "action": "<action>"
    },
    "name": "connections_mark"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe connection's LinkedIn profile URL, as in Connections.csv.
noteNoA short note, kept with the mark. For a warning, the text LinkedIn showed.
actionYeskeep or remove: override the rating. removed or skipped: the outcome. warning: LinkedIn showed a warning.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A3.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations, the description discloses the crucial fact that 'It removes nothing on LinkedIn', which prevents an agent from assuming a 'remove' mark actually un-connects anyone, and it explains that a warning writes the LINKEN_HALT_FILE halt file that disables four other tools. That is substantial behavioral context the annotations (destructiveHint=false) do not convey. It does not say whether marks are idempotent or overwrite prior marks, keeping it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded in the first clause, and the side-effect warnings follow in a logical order. It is a single long, dense sentence that is slightly run-on but contains no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter write tool with no output schema, the description covers the important behavioral surface: local-only semantics, the halt-file side effect, and the downstream tools affected. Missing only return-value and idempotency details, which are minor here.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already defines url, note, and every action enum value; the description's action explanations largely restate the schema's own text. Baseline 3 applies since the description adds little new parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ('Records the owner's decision for one connection') and then enumerates what each action value means. It does not explicitly contrast itself with siblings like connections_next or inbox_mark, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: you mark a connection after a person keeps, removes, skips, or gets warned. There is no explicit 'use this when / use X instead' routing, though the warning action's consequences (halting connections_next, post_publish, comment_create, reply_open) give real context for when that path applies.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.