Skip to main content
Glama

LinkedIn: Update my profile

linkedin_update_my_profile
Destructive

Update supported fields of the user's own LinkedIn profile. Only pass fields explicitly requested by the user; provider support varies by field.

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

Input Schema

NameRequiredDescriptionDefault
bioNo
pictureNo
summaryNo
headlineNo
locationNo
specificsNo
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.
background_pictureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedInput schema / additionalProperties
      Previous value: -{}New value: +false
    • addedInput schema / properties / background_picture
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "content": {
      +      "type": "string"
      +    },
      +    "content_type": {
      +      "type": "string"
      +    },
      +    "filename": {
      +      "type": "string"
      +    },
      +    "metadata": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "duration": {
      +          "type": "number"
      +        }
      +      },
      +      "type": "object"
      +    }
      +  },
      +  "required": [
      +    "content",
      +    "content_type",
      +    "filename"
      +  ],
      +  "type": "object"
      +}
    • addedInput schema / properties / bio
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / first_name
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / last_name
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / picture
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "content": {
      +      "type": "string"
      +    },
      +    "content_type": {
      +      "type": "string"
      +    },
      +    "filename": {
      +      "type": "string"
      +    },
      +    "metadata": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "duration": {
      +          "type": "number"
      +        }
      +      },
      +      "type": "object"
      +    }
      +  },
      +  "required": [
      +    "content",
      +    "content_type",
      +    "filename"
      +  ],
      +  "type": "object"
      +}
    • addedInput schema / properties / specifics
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "linkedin": {
      +      "additionalProperties": {},
      +      "propertyNames": {
      +        "type": "string"
      +      },
      +      "type": "object"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is largely covered. The description adds a genuinely useful caveat that provider support varies by field, but says nothing about irreversibility, whether omitted fields are preserved, or what happens on partial failure — relevant gaps for a destructive mutation.

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?

Two tight sentences, with the action front-loaded and the constraint following. No filler. It could still have spent one more sentence on field semantics without becoming verbose, but nothing present is wasted.

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?

With 8 parameters, nested objects, no output schema, and a destructive mutation flag, the description is too thin — it never explains the opaque 'specifics' object or how image content must be supplied. An agent could call it, but would likely misfill nested arguments or omit required context.

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?

Schema description coverage is only 13%, so the description carries the burden of explaining parameters, yet it adds essentially nothing about bio vs. summary vs. headline, the nested 'specifics.linkedin' escape hatch, or the picture/background_picture content encoding. Only 'provider support varies by field' gives a hint about field semantics.

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 states a specific verb and resource ('Update supported fields of the user's own LinkedIn profile'), scoping it to the caller's own profile rather than arbitrary people. It clearly separates itself from read siblings like linkedin_get_my_profile, though it does not name those siblings explicitly.

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?

It gives a useful partial-update rule ('Only pass fields explicitly requested by the user'), which tells the agent how to populate arguments. However, it offers no guidance on when to use this versus reading the profile first, or how to confirm which fields the provider supports.

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.