Skip to main content
Glama
Sign In
linkedin-pilot

linkedin-pilot

by juanpacj-wq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

linkedin_follow

Follow or unfollow a LinkedIn profile by providing the target; confirm=true is required to execute the action.

Instructions

Sigue o deja de seguir un perfil. Exige confirm=true.

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": {
      "target": "<target>"
    },
    "name": "linkedin_follow"
  }
}

Input Schema

NameRequiredDescriptionDefault
followNotrue para seguir (por defecto), false para dejar de seguir.
targetYes
confirmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose one meaningful behavioral requirement — that confirm=true is mandatory before the action executes — which is a safety guard the schema does not explain. It omits side effects (does following notify the target?), reversibility, and any rate limits or auth requirements.

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?

Two short sentences with no filler, and the confirm precondition is front-loaded so an agent cannot miss it. Nothing could be removed without losing information.

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?

This is a mutating social action with no annotations, no output schema, and an undocumented required parameter. The description says nothing about result behavior, errors when confirm is omitted, or whether the operation is idempotent, leaving real gaps for a write 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 only 33% and the required 'target' parameter has no description at all. The description partially compensates by clarifying follow's direction and the mandatory confirm flag, but it adds nothing about what form 'target' takes (vanity name, URL, URN) or its accepted syntax.

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 names a specific verb pair and resource: follow or unfollow a profile. That is unambiguous. It does not, however, distinguish itself from adjacent siblings like linkedin_connect or linkedin_endorse, which involve related social actions on profiles.

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?

There is no guidance on when to follow versus when to use linkedin_connect (connection request) or any other sibling, and no stated preconditions beyond the confirm flag. Usage must be inferred purely from the verb.

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