Skip to main content
Glama
Sign In

Bridgly

by app.bridgly.mcp
OverviewDiscussionsAdmin

Fetch a LinkedIn company by company slug

linkedin_get_company_from_url
Read-onlyIdempotent

Get a LinkedIn company page from the slug in its URL, e.g. "openai". Returns the name, tagline, description, industry, employee count, headquarters and other locations, website, follower count, specialties, funding details and similar companies. Read-only: returns public data and changes nothing. Costs 1 credit per request.

Input Schema

NameRequiredDescriptionDefault
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.
universalNameYesThe company's LinkedIn universal name — the slug in linkedin.com/company/<universalName> — or the company, school or showcase page link itself, e.g. "openai" or "https://www.linkedin.com/company/openai".
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
    • 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"
+}
  2. 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, idempotentHint, openWorldHint and destructiveHint=false, so the 'read-only: changes nothing' sentence adds no new information. What the description does add beyond structured data is the cost model ('Costs 1 credit per request') and the scope of returned public data, both genuinely useful for planning calls.

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 front-loaded sentences: purpose and input example first, return payload second, safety and cost last. Tight overall, though the read-only sentence largely restates the annotations and could be trimmed or replaced with cost/caching guidance.

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 compensates by enumerating the returned fields (name, tagline, industry, employee count, locations, followers, funding, similar companies), which is exactly what an agent needs to decide whether this tool satisfies an information need. Cost and read-only semantics round it out.

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% and the schema already documents universalName with the same 'openai' example and fully explains cacheOnly and cacheMaxAgeHours. The description therefore adds essentially nothing about parameters beyond what the schema provides, so the 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 ('Get a LinkedIn company page from the slug in its URL') and disambiguates the input with a concrete example ('openai'). It is clearly distinguishable from linkedin_search_companies (search vs. fetch) and from profile-oriented siblings by resource type.

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?

Usage is implied: call it when you already have a company slug or company page URL. The description never says when to prefer this over linkedin_search_companies or linkedin_get_posts_from_company, and gives no exclusion guidance for the cache parameters that control cost.

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