Skip to main content
Glama
Sign In
linkedin-pilot

linkedin-pilot

by juanpacj-wq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

linkedin_profile_sections

Lists editable LinkedIn profile sections and their typical fields, so you know what profile data can be updated.

Instructions

Lista las secciones del perfil que se pueden editar, con los campos habituales de cada una.

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_profile_sections"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/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 disclosure burden. It conveys the returned content (editable sections and their typical fields) and implies a read-only enumeration, but says nothing about login/session requirements, whether it reflects live profile state, or rate/latency behavior.

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 with zero filler and the core purpose front-loaded. It is appropriately sized for a zero-parameter discovery tool, though it could be marginally more explicit about scope.

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?

With no output schema and no annotations, the description is the sole source of return-value information, and it only roughly sketches the shape ('sections...with usual fields'). It is adequate for a simple enumerator but leaves the exact output structure and any prerequisites underspecified.

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 for the description to compensate for; the baseline is 4. The description correctly indicates no input is required to enumerate the sections.

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 ('Lista') and resource (profile sections) plus the payload content (usual fields per section). It is distinguishable from pure readers like linkedin_profile_read and mutators like linkedin_profile_edit, though it does not explicitly name those siblings as alternatives.

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

Usage Guidelines3/5

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

No explicit when-to-use or when-not-to-use is given, but the 'sections that can be edited' framing implies it is a discovery step before editing. The agent must infer that this is a precursor to the profile_edit family rather than being told.

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