Skip to main content
Glama
Sign In
linkedin-pilot

linkedin-pilot

by juanpacj-wq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

linkedin_session_status

Check whether a LinkedIn session is active in the persistent browser and return the member name, public ID, and cookie expiry. Run this before any other LinkedIn action.

Instructions

Comprueba si hay sesión de LinkedIn activa en el navegador persistente. Devuelve el nombre, el identificador público y cuándo caduca la cookie. Llama a esto antes que nada.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "linkedin_session_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses that the session lives in a persistent browser and enumerates the return payload (name, public identifier, cookie expiry). It does not say how a missing/expired session is surfaced (error vs. empty result), which is the remaining gap.

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

Conciseness5/5

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

Three short sentences, no wasted words. The purpose leads, the return values follow, and the caller instruction is last — a well-ordered, front-loaded block.

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 no-parameter status probe with no output schema, the description covers purpose, payload, and call ordering adequately. The only omission is the failure/absent-session behaviour an agent would need to branch on.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing to document and the baseline of 4 applies. The description correctly adds no parameter noise.

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 a specific verb and resource: it checks whether an active LinkedIn session exists in the persistent browser. It also names the returned fields, making the read-only nature unmistakable, though it does not explicitly distinguish itself from neighbours like linkedin_login or linkedin_session_cookies.

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?

"Llama a esto antes que nada" gives explicit ordering guidance — call it first, before any authenticated action. It stops short of naming alternatives or stating what to do if no session is found, so it is clear context without full exclusion logic.

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