Bridgly

List the honors and awards of a LinkedIn profile

linkedin_get_profile_honors

Read-onlyIdempotent

List every honor and award on a LinkedIn member's profile, with the issuer, issue date and description. 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_honors"
  }
}

Input Schema

Name	Required	Description
`count`	Yes	Number of results to return (1–100). Defaults to 100.
`start`	No	Number of results to skip. Defaults to 0.
`publicId`	Yes	The member public identity, or the profile link itself, e.g. "williamhgates" or "https://www.linkedin.com/in/williamhgates".
`cacheOnly`	No	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.
`cacheMaxAgeHours`	No	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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 10, 2026

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."

Changed2 schema fields changedNov 7, 2026

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

AddedNov 5, 2026

TDQS

A3.7/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 largely covered; the description still adds real value by confirming it returns public data and "changes nothing" and by disclosing a cost of 1 credit per request, which is not in the annotations. The blanket "Costs 1 credit per request" sits slightly awkwardly against the schema's statement that cached reads cost no credits, and it does not mention pagination limits or error behavior.

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?

Four short, front-loaded sentences: purpose first, then pagination, safety, and cost, with no filler. The only cost is the ambiguous `nextStart` reference, which is a correctness issue rather than verbosity.

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 enumerating issuer, issue date and description, plus output shape via pagination. Missing pieces are minor: no explicit note that results are limited to 100 per call in prose (the schema covers it) and no explanation of the cache-versus-live cost path, though the schema documents that fully.

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%, so baseline is 3 and the schema already explains publicId, count, start, cacheOnly and cacheMaxAgeHours in detail. The description adds nothing beyond pagination — and it refers to `nextStart`, which does not match the schema's `start` parameter, a naming mismatch that could confuse an agent building the follow-up call.

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?

"List every honor and award on a LinkedIn member's profile, with the issuer, issue date and description" names a specific verb, resource, and returned fields, so the agent knows exactly what data comes back. It never names a sibling (e.g. linkedin_get_profile_certifications or linkedin_get_profile_publications), so differentiation relies on the resource noun in the name rather than explicit routing.

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 one concrete operational instruction — continue paging with the `nextStart` from the previous response — which is real usage guidance for result sets over 100. It offers no when-to-use versus when-not guidance and no mention of the cacheOnly/cacheMaxAgeHours tradeoff covered in the schema, leaving the choice between live scrape and cache unexplained at the description level.

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

All Bridgly tools Inspect

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

Need Help?