Skip to main content
Glama

LinkedIn: Endorse skill

linkedin_endorse_skill
Destructive

Endorse one skill on a LinkedIn relation. Resolve member_id first, fetch that profile with linkedin_skills, and reuse the exact returned endorsement skill_id; never pass a skill name.

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": {
      "member_id": "<member_id>",
      "skill_id": "<skill_id>"
    },
    "name": "linkedin_endorse_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
skill_idYesExact endorsement skill ID from the member profile's linkedin_skills section; not the display name.
member_idYesExact LinkedIn member profile ID returned by the profile resolver; not a URL/name.
account_idNoOptional Nilyo connection ID (unipile_account_id from list_connected_accounts). Omit when the user has one account for this provider. When several exist, Nilyo never guesses: list them (display name, identifier, provider user ID), choose the one the user named or ask, and pass its ID here.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already flag this as a non-idempotent, destructive, open-world write, so the safety profile is covered structurally. The description adds useful preconditions but says nothing about what the endorsement does publicly, whether it can be undone, or what happens on a repeat endorsement (despite idempotentHint=false).

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 sentences, each earning its place: the first states the action, the second states the required lookup order. The critical constraint is front-loaded and nothing is padded.

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 three-parameter write tool with full schema coverage and no output schema, the definition covers purpose and lookup ordering. The one gap is that it references 'linkedin_skills' without tying it to a concrete sibling tool, leaving the agent to infer which call returns that payload.

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 100% and the field descriptions already state 'exact endorsement skill ID… not the display name' and the member_id provenance. The description's 'never pass a skill name' and 'reuse the exact returned skill_id' restate that same constraint, adding emphasis rather than new meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Endorse one skill on a LinkedIn relation" is a precise verb+resource pair with an explicit cardinality ('one skill'), and no sibling tool competes with it, so an agent can identify it immediately.

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?

It prescribes a concrete prerequisite chain: resolve member_id, fetch the profile with linkedin_skills, then reuse the returned skill_id. What is missing is the negative case — it doesn't name which resolver tool to use for member_id or what to do if the profile exposes no matching skill.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.