Bridgly

List the volunteer experience of a LinkedIn profile

linkedin_get_profile_volunteering

Read-onlyIdempotent

List every volunteer role on a LinkedIn member's profile, with the organization, cause, dates 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_volunteering"
  }
}

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

A4.3/5.0

Behavior4/5

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

The read-only claim largely restates the readOnlyHint/destructiveHint annotations, but the description adds two facts not in structured data: results are public data only, and each request costs 1 credit. Cost-per-call is meaningful behavioral context for a scraping tool with openWorldHint. It stops short of describing failure modes (e.g., private or empty profiles) or how `cacheOnly`/`cacheMaxAgeHours` affect billing.

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 short sentences, zero filler: what is returned first, then pagination, then safety and cost. Every sentence carries a distinct, actionable fact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 still states the shape of a returned role and how to continue paging, plus the cost and read-only profile. For a 5-parameter listing tool whose parameters are fully documented in the schema, nothing an agent needs to call it correctly is missing.

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 meaning of `publicId`, `count`, `start`, `cacheOnly` and `cacheMaxAgeHours` is already fully documented in the schema; baseline 3 applies. The description's only parameter-adjacent contribution is pagination via `nextStart`, which is a response field name rather than a parameter and is not the same token as the `start` input, so it does not enrich the schema's semantics.

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?

"List every volunteer role on a LinkedIn member's profile" gives a specific verb and a precisely scoped resource, and it enumerates the returned fields (organization, cause, dates, description). Against siblings like linkedin_get_profile_education or linkedin_get_profile_certifications, an agent can immediately tell which profile section this covers.

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?

"Page on with the `nextStart` from the previous response" is concrete continuation guidance that an agent would otherwise have to discover by trial. It gives clear context for repeated invocation, but offers no explicit exclusions or naming of an alternative tool when a different profile section is needed.

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?