Skip to main content
Glama
Sign In

Bridgly

by app.bridgly.mcp
OverviewDiscussionsAdmin

List the skills of a LinkedIn profile

linkedin_get_profile_skills
Read-onlyIdempotent

List every skill on a LinkedIn member's profile, in the order the profile shows them, with how many members endorsed each. Page on with the nextStart from the previous response. Read-only: returns public data and changes nothing. Costs 1 credit per request.

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": {
      "publicId": "<publicId>",
      "count": "<count>"
    },
    "name": "linkedin_get_profile_skills"
  }
}

Input Schema

NameRequiredDescriptionDefault
countYesNumber of results to return (1–100). Defaults to 100.
startNoNumber of results to skip. Defaults to 0.
publicIdYesThe member public identity, or the profile link itself, e.g. "williamhgates" or "https://www.linkedin.com/in/williamhgates".
cacheOnlyNoReturn only a cached result and never scrape live. With `cacheMaxAgeHours`, only a result that recent is returned; without it, the latest cached result of any age. Responds 404, at no cost, when there is none, e.g. true.
cacheMaxAgeHoursNoAccept a cached result scraped up to this many hours ago. A cached result costs no credits, and its `cachedAt` says when it was scraped. When no cached result is that recent, the data is scraped live at the normal price. Leave it out to always scrape live, e.g. 24.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / count / default
      Previous value: -10New value: +100
    • changedInput schema / properties / count / description
      Previous value: -"Number of results to return (1–100). Defaults to 10."New value: +"Number of results to return (1–100). Defaults to 100."
  2. Changed2 schema fields changed
    • addedInput schema / properties / cacheMaxAgeHours
      Added value: +{
+  "description": "Accept a cached result scraped up to this many hours ago. A cached result costs no credits, and its `cachedAt` says when it was scraped. When no cached result is that recent, the data is scraped live at the normal price. Leave it out to always scrape live, e.g. 24.",
+  "exclusiveMinimum": 0,
+  "maximum": 9007199254740991,
+  "type": "integer"
+}
    • addedInput schema / properties / cacheOnly
      Added value: +{
+  "description": "Return only a cached result and never scrape live. With `cacheMaxAgeHours`, only a result that recent is returned; without it, the latest cached result of any age. Responds 404, at no cost, when there is none, e.g. true.",
+  "type": "boolean"
+}
  3. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered; the description still earns credit by adding the result ordering guarantee, the endorsement-count field, the pagination continuation token, and an explicit cost of 1 credit per request. It stops short of noting caching behavior for the cacheOnly path, which is left to the schema.

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?

Four short clauses, front-loaded with the resource and the returned shape, then pagination, then safety, then cost. No sentence restates the title 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?

With no output schema, the description carries the return-value burden and does so by naming the ordering, endorsement counts and the nextStart continuation field. Cost and read-only behavior are covered too. Only the cache-only path's semantics are absent, and those are fully specified in the schema.

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 count, start, publicId and the cache parameters are already documented in structured fields. The description only adds the paging idiom (use nextStart from the prior response), which is a return-value hint more than parameter semantics. Baseline 3 applies.

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?

States a specific verb and resource ("List every skill on a LinkedIn member's profile") plus the exact shape of what comes back: ordering as shown on the profile and endorsement counts. Against siblings like linkedin_get_profile_certifications or linkedin_get_profile_experience, the resource distinction 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 concrete operational guidance for continuing a result set ("Page on with the `nextStart` from the previous response") and states the credit cost, but never names an alternative or a condition for choosing this profile sub-resource over another. Usage is implied by the resource name rather than taught.

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

All Bridgly toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources