Skip to main content
Glama
Sign In
linkedin-pilot

linkedin-pilot

by juanpacj-wq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

linkedin_browser_navigate

Navigate to any LinkedIn URL and return the page's full snapshot, enabling AI agents to load profiles, feeds, or job pages within a persistent browser session.

Instructions

Navega a una URL de LinkedIn y devuelve la radiografía de la página.

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>"
    },
    "name": "linkedin_browser_navigate"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden, yet it only says it returns a page 'radiografía'. It omits auth/session requirements, whether navigation triggers a browser launch, how redirects or rate limits are handled, and what the returned snapshot actually contains.

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?

A single compact sentence that front-loads the action and result with no wasted words. Its brevity is a virtue here, though only because so little is stated.

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

Completeness2/5

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

For a navigation tool with no annotations, no output schema, and no parameter documentation, the description is too thin. An agent cannot know it needs an authenticated session or what the returned 'radiografía' comprises before calling it.

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

Parameters2/5

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

The single 'url' parameter is undocumented in the schema (0% coverage). The description adds the constraint that the URL must be LinkedIn, but given the tool name already implies LinkedIn, this is marginal and no format or example is given.

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 ('Navega') and resource ('una URL de LinkedIn') plus a return value ('la radiografía de la página'). An agent can tell it navigates a browser, though it does not contrast itself with the closely related 'linkedin_browser_snapshot', which also returns page content.

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

Usage Guidelines2/5

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

No guidance on when to use this versus alternatives such as linkedin_browser_snapshot, linkedin_browser_click, or the profile/login tools. No prerequisites (an active logged-in session) are mentioned, leaving the agent to infer context.

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