Skip to main content
Glama

Load a LinkedIn data export

archive_load

Reads a LinkedIn data export (ZIP or folder) to rate connections by configurable rules, save results under LINKEN_HOME, return tier/reason counts and date range, and flag inbox threads awaiting you.

Instructions

Reads a LinkedIn data export, the .zip or its unpacked folder, rates every connection with the rules in rules/rater.default.json plus the optional LINKEN_RATER overlay, and saves the result under LINKEN_HOME, with the message threads waiting on the member for inbox_next. A zip is unpacked into LINKEN_HOME/archive. Returns counts by tier and by reason and the export date range. A newer export keeps earlier marks and states. It does not contact LinkedIn and changes no connection.

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": {
      "path": "<path>"
    },
    "name": "archive_load"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute path to the export .zip or to the unpacked folder.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A4.4/5.0
Behavior5/5

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

Goes well past the annotations: it discloses side effects (zip unpacked into LINKEN_HOME/archive, results saved under LINKEN_HOME), a merge/re-run policy ('a newer export keeps earlier marks and states'), and the return payload shape (counts by tier and reason, export date range). The 'does not contact LinkedIn and changes no connection' clause reconciles the mutation-implying readOnlyHint=false with a safe, non-destructive local write.

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?

Front-loaded with the core verb and resource, and each following clause (rules, overlay, output location, return counts, non-destructiveness) carries distinct information. The embedding of 'with the message threads waiting on the member for inbox_next' mid-sentence is syntactically awkward and could be its own short lead-out.

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

Completeness5/5

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

For a one-parameter tool with no output schema, the description supplies everything needed: what it reads, where it writes, what rules it applies, what the return counts are, and how re-runs merge. Nothing material for correct invocation is missing.

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?

With a single required parameter at 100% schema coverage, the schema already documents that path is an absolute path to the .zip or unpacked folder, and the description largely repeats that distinction. It adds only the incidental detail that a zip is unpacked into LINKEN_HOME/archive, which is behavioral rather than parameter-shaping.

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

Purpose5/5

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

States a concrete verb+resource ('Reads a LinkedIn data export') and then enumerates the full pipeline: rating every connection with rules/rater.default.json plus the optional LINKEN_RATER overlay, saving under LINKEN_HOME, and surfacing threads for inbox_next. An agent can distinguish this from connections_* and inbox_* siblings purely from the description.

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

Usage Guidelines4/5

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

Clear operating context: accepts a .zip or unpacked folder, requires LINKEN_HOME, and explicitly states it does not contact LinkedIn and changes no connection, which tells the agent this is a safe local prepare/rate step. It also gestures at the follow-up (message threads waiting for inbox_next), but never names an alternative tool to use instead when the export is already loaded or when only re-rating is wanted.

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