Bridgly

List the schools a LinkedIn profile follows

linkedin_get_profile_interests_schools

Read-onlyIdempotent

List the schools from the interests section of a LinkedIn member's profile, each with its name, page link, logo and follower count. 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_interests_schools"
  }
}

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.9/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 "Read-only: returns public data and changes nothing" largely restates them. However, the description adds information not present in structured fields: credit cost per request ("Costs 1 credit per request") and the pagination contract, which are the operationally important behaviors for this paid scraping API.

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?

Three short sentences, front-loaded with the purpose, then paging, then safety/cost — a logical ordering with no filler. The read-only clause is the one fragment that mostly duplicates annotations and could be trimmed.

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 usefully enumerates what each result contains and how to page, and the credit cost covers the main unstated risk. What it omits — caching behavior and the 404-at-no-cost path — is fully covered by the schema's parameter descriptions, so nothing critical 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 all five parameters (including cacheOnly and cacheMaxAgeHours) are already well documented, making 3 the baseline. The description's only parameter-adjacent statement references `nextStart` from the response rather than the schema's `start` parameter, so it adds little semantic clarity and slightly muddies naming.

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 the schools from the interests section of a LinkedIn member's profile") and enumerates the returned fields (name, page link, logo, follower count), which distinguishes it cleanly from siblings like linkedin_get_profile_interests_companies, _groups and _newsletters.

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 paging guidance ("Page on with the `nextStart` from the previous response"), which is genuine how-to-use context, but there is no explicit when-to-use versus the closely named siblings such as linkedin_search_schools or the other interests endpoints. Usage is implied by the tool name more than stated.

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?