Skip to main content
Glama
Sign In
linkedin-pilot

linkedin-pilot

by juanpacj-wq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

linkedin_session_cookies

Export LinkedIn session cookies to back up login state, or import li_at and JSESSIONID to resume a session without signing in.

Instructions

Exporta las cookies de la sesión a un archivo, o importa un li_at/JSESSIONID obtenido del navegador personal. Útil para respaldar la sesión o para arrancar sin pasar por el login.

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": {
      "action": "<action>"
    },
    "name": "linkedin_session_cookies"
  }
}

Input Schema

NameRequiredDescriptionDefault
liAtNoValor de la cookie li_at (solo para import).
actionYes
filePathNoRuta del archivo JSON de cookies.
jsessionidNoValor de la cookie JSESSIONID (solo para import).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that import consumes a li_at/JSESSIONID from the personal browser and that this lets the session start without login, but says nothing about permission requirements, what happens to an existing session on import, or the sensitivity/storage risks of exported cookies.

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?

Two tight sentences, front-loading the export/import duality before the use case. Little waste, though the 'útil para' clause is somewhat soft.

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

Completeness3/5

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

No output schema and no annotations, so the description must stand alone; it explains the two actions and their rationale but omits return/error behavior and any file-format guidance beyond what the schema implies. Adequate but with clear gaps for a session-credential tool.

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 coverage is 75% and the schema already documents liAt, jsessionid and filePath. The description reinforces that li_at/JSESSIONID are import-only and originate from the personal browser, but adds no format or constraint detail beyond the schema, so baseline 3 applies.

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?

States specific verbs (export/import) on a specific resource (session cookies), and its purpose is clearly distinct from siblings like linkedin_login and linkedin_session_status. It does not explicitly name those siblings, so it stops short of full differentiation.

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?

Gives clear use cases: backing up the session or starting without going through login. It tells the agent when this is the right tool, though it names no alternatives or exclusions (e.g. when to prefer linkedin_login instead).

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

Deploy Server

Other Tools