Skip to main content
Glama

Nilyo

by com.nilyo
OverviewDiscussionsAdmin

LinkedIn: Update my profile

linkedin_update_my_profile

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

Input Schema

TableJSON 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.2/5.0
Behavior3/5

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

Annotations already declare write semantics (readOnlyHint=false), non-idempotency, and non-destructiveness, so the safety profile is covered. The description adds one piece of genuine behavioral context — 'provider support varies by field,' implying partial/possibly-silent field application — but does not say what happens to unsupported fields, auth requirements, or whether a partial update is atomic.

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 tight sentences with no filler, and the load-bearing constraint ('only pass fields explicitly requested') is placed prominently. Nothing is redundant or padding.

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 an 8-parameter mutation tool with no output schema and near-zero schema documentation, the description is far too thin. It omits which fields are supported, how nested objects should be shaped, and what the agent should do when a field is unsupported — the exact gaps that matter before an agent calls a profile-write tool.

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 coverage is only 13% (basically only account_id is documented in-schema), so the description is expected to compensate and does not. It never names the updatable fields (bio, headline, summary, location, picture, background_picture, specifics) nor explains the nested picture/background_picture or specifics structure, leaving 7 of 8 parameters semantically thin.

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 clear verb+resource: 'Update supported fields of the user's own LinkedIn profile.' The 'own profile' scope distinguishes it from the many sibling read/search tools and from profile-viewing tools. It could be sharper about which fields are 'supported,' but the core purpose is unambiguous.

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?

Gives one real usage rule — 'Only pass fields explicitly requested by the user' — which constrains behavior and prevents unwanted edits. However, it names no alternatives (e.g., how it differs from other profile-writing flows) and offers no when-not-to-use guidance, so usage is implied rather than fully specified.

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

All Nilyo toolsInspect
Try in Browser
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources