Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

linkedin_update_profile

Update the authenticated user's own LinkedIn profile. Supports adding/editing experience entries (role, company, skills, dates). Also supports updating location. Headline, summary, education are NOT supported by the API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locationNoLocation to set on profile (requires LinkedIn location ID)
experienceNoAdd or edit a professional experience entry
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
+  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
+  "type": "integer"
+}
  2. Added
  3. Removed
  4. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: the operation is scoped to the authenticated user's own profile (an auth/ownership constraint) and it discloses hard API-side field limitations. It does not discuss reversibility, required scopes, or partial-update behavior.

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?

Three tight sentences, front-loaded with the operation and scope, then supported fields, then the exclusion list. Every sentence carries distinct information and the negative constraint in the final sentence earns its place by preventing wasted calls.

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 mutation tool with no output schema but full annotation coverage, the description covers ownership scope, supported and unsupported fields, and the add-vs-edit intent. Minor gaps remain: no mention of what a successful response contains or whether a call with no arguments is a no-op, but these are secondary given the schema and annotations.

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 description coverage is 100%, so the nested location/experience objects, the location ID requirement and the add-vs-edit id semantics are already fully documented in the schema. The description restates the same field set (role, company, skills, dates; location) without adding format, ordering, or interaction detail. Baseline 3 applies.

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 and resource ('Update the authenticated user's own LinkedIn profile') and enumerates exactly which sub-resources are supported (experience entries, location) versus not (headline, summary, education). The scope qualifier 'authenticated user's own' pins it down well, though no sibling tool (e.g. linkedin_raw_request) is named as the fallback for the unsupported fields.

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?

Gives clear when-to-use conditions (adding/editing experience, updating location) and an explicit when-not ('Headline, summary, education are NOT supported by the API'). It stops short of naming the alternative tool an agent should reach for those unsupported fields, so routing is implied rather than complete.

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

All dialogbrain toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources