Server Details
LinkedIn data for AI agents: search, profiles, companies, posts. No key needed to start.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.8/5 across 6 of 6 tools scored.
Each tool targets a unique resource or action: company, posts, profile, usage, URL resolution, and people search. No two tools have overlapping functionality; descriptions clearly differentiate them.
All tool names follow a consistent verb_noun pattern (get_company, get_posts, get_profile, get_usage, resolve_url, search_people). The naming is uniform and predictable.
With 6 tools, the server is well-scoped for LinkedIn data extraction. Each tool serves a distinct purpose without being too few or too many.
The tool set covers major LinkedIn resources: company, profile, posts, and people search. Minor gaps exist (e.g., no tool for fetching a specific post by URL or searching companies), but core workflows are supported.
Available Tools
6 toolsget_usageCheck credits and recent chargesARead-onlyInspect
Check your balance, plan, limits, and the last 10 charges (receipt ids included). Costs 0 credits and is exempt from the per-minute rate limit, so call it whenever you need to budget. The response includes upgrade_url (give it to your human when credits or plan limits block you; purchases credit this account directly with no login) and manage_url (give it to your human to change or cancel a paid plan in the Stripe billing portal). Trial accounts also get a claim_url that attaches an email so the account can be recovered if the key is lost. Requires an API key: keyless calls have no account, and each keyless response already reports its cost in the usage block. Not for fetching LinkedIn data.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| usage | Yes | |
| common | Yes | |
| entity | Yes | |
| platform | Yes | |
| freshness | Yes | |
| data_as_of | Yes | |
| canonical_url | Yes | |
| schema_version | Yes | |
| platform_fields | Yes |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnly and idempotent. Description adds value: costs 0 credits, exempt from rate limit, includes upgrade_url and manage_url, and distinguishes keyless vs API key behavior. No contradictions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Description is somewhat lengthy but every sentence adds unique value (cost, URLs, keyless distinction, negative use). Well-structured: starts with core purpose, then cost/limits, then URLs, then edge cases. Could slightly tighten but still efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no parameters, strong annotations, and presence of output schema, the description is fully complete. It covers purpose, usage, behavioral traits, edge cases, and integration points (URLs). No gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Zero parameters in schema, so no additional param info needed. Baseline of 4 applies. Description does not require parameter semantics as there are none.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the tool checks balance, plan, limits, and last 10 charges. The verb 'check' and specific resources are explicitly listed. No overlap with siblings like get_company or search_people, so it's well-differentiated.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says when to use: 'call it whenever you need to budget.' Also notes cost (0 credits) and rate limit exemption. States 'Not for fetching LinkedIn data', which helps avoid misuse. Provides guidance on URLs for human interactions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
linkedin_get_companyGet a LinkedIn companyRead-onlyInspect
Fetch one company's LinkedIn page: name, description, industry, employee count, headquarters, website, founding year, specialities, and the URN/numeric id you need for linkedin_search_people company filters. identifier accepts a company URL, the slug after /company/ (e.g. 'microsoft'), or a website domain like 'microsoft.com'; numeric ids and URNs are search-filter inputs, not fetch identifiers. Domains are resolved to a company and verified against that company's website: a domain identifier always QUOTES base+4 credits (set max_credits accordingly), and the 4-credit resolution surcharge is refunded at settlement when the domain was resolved before, so known domains settle at the base price. A domain that cannot be verified to a company returns INVALID_INPUT with the closest matches instead of a guessed company. Costs 4 credits base. This tool does not search by name: if you only have an approximate company name, use linkedin_search_people's current_company filter with keywords (the filter resolves names) or give the exact slug. For the company's posts, use linkedin_get_posts with the same identifier (URL, slug, or website domain all work there too).
| Name | Required | Description | Default |
|---|---|---|---|
| freshness | No | ||
| identifier | Yes | Company URL, slug (after /company/), or website domain (e.g. 'microsoft.com'). Numeric ids/URNs are not fetchable; use them only in linkedin_search_people company filters. | |
| max_credits | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| usage | Yes | |
| common | Yes | |
| entity | Yes | |
| platform | Yes | |
| freshness | Yes | |
| data_as_of | Yes | |
| canonical_url | Yes | |
| schema_version | Yes | |
| platform_fields | Yes |
linkedin_get_postsGet recent posts by a person or companyRead-onlyInspect
Fetch the recent LinkedIn posts of one person or one company. identifier accepts a profile or company URL, a slug, a person URN, or a company website domain like 'microsoft.com'; the entity type is detected automatically. A domain resolves to its verified company first, exactly like linkedin_get_company: it QUOTES base+4 credits (set max_credits accordingly) and the surcharge is refunded at settlement for already-known domains, so they settle at the base price. Company URNs and numeric company ids are search-filter inputs, not fetch identifiers: use the company slug, URL, or domain here. Returns one page of posts (text, created_at, author, likes, comments_count, shares, is_repost, url) with a cursor for older posts. Costs 4 credits per page. Use this for 'what has X been posting', voice-of-company research, or activity checks before outreach. Not for reading one specific post you already have a URL for, and not for keyword search across LinkedIn; neither is supported in v1.
| Name | Required | Description | Default |
|---|---|---|---|
| cursor | No | ||
| freshness | No | ||
| identifier | Yes | Person or company URL, slug, URN, or company website domain. | |
| max_credits | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| usage | Yes | |
| common | Yes | |
| entity | Yes | |
| platform | Yes | |
| freshness | Yes | |
| data_as_of | Yes | |
| canonical_url | Yes | |
| schema_version | Yes | |
| platform_fields | Yes |
linkedin_get_profileGet a LinkedIn person profileRead-onlyInspect
Fetch one person's LinkedIn profile. identifier accepts a profile URL, the slug after /in/ (e.g. 'williamhgates'), or a urn:li:fsd_profile URN; URLs are cleaned automatically. Always returns the overview (name, headline, location, current position, follower counts) plus up to 2 requested sections from about|experience|education|skills at no extra cost; each section beyond 2 adds 2 credits (max 4 sections). Costs 4 credits base. If you only have a name, use linkedin_search_people first; this tool does not search. Results from linkedin_search_people with is_anonymous=true cannot be fetched here; treat them as 'someone matching this exists' and stop. Companies belong to linkedin_get_company.
| Name | Required | Description | Default |
|---|---|---|---|
| sections | No | ||
| freshness | No | ||
| identifier | Yes | Profile URL, slug (after /in/), or urn:li:fsd_profile URN. | |
| max_credits | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| usage | Yes | |
| common | Yes | |
| entity | Yes | |
| platform | Yes | |
| freshness | Yes | |
| data_as_of | Yes | |
| canonical_url | Yes | |
| schema_version | Yes | |
| platform_fields | Yes |
linkedin_resolve_urlIdentify a LinkedIn URLRead-onlyInspect
Identify what a LinkedIn URL points at before fetching it. Give any LinkedIn profile, company, or post URL (utm params, www/m subdomains, trailing slashes are fine); get back {type: person|company|post, id, handle, canonical_url}. For profile URLs, id is the stable person URN; for company URLs, id is the stable company URN; for post URLs, id is the activity URN extracted from the URL. For people, use the returned handle or id with linkedin_get_profile or linkedin_get_posts. For companies, use the returned HANDLE with linkedin_get_company or linkedin_get_posts; the company URN/id is a linkedin_search_people filter input, not a fetch identifier. Costs 2 credits. Skip this tool when you already have a slug, URN, or clean URL: linkedin_get_profile and linkedin_get_company accept those directly, so resolving first would waste 2 credits. Not for non-LinkedIn URLs; it returns INVALID_INPUT for those.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | A LinkedIn URL, e.g. https://www.linkedin.com/in/williamhgates or .../company/microsoft. |
Output Schema
| Name | Required | Description |
|---|---|---|
| usage | Yes | |
| common | Yes | |
| entity | Yes | |
| platform | Yes | |
| freshness | Yes | |
| data_as_of | Yes | |
| canonical_url | Yes | |
| schema_version | Yes | |
| platform_fields | Yes |
linkedin_search_peopleSearch people on LinkedInRead-onlyInspect
Find people on LinkedIn by keywords and filters. The right tool when you have a name, role, or 'who is the X at Y' question without a profile URL. Pass keywords (free text: name, title, or both) and any of first_name, last_name, title, school, current_company, past_company. If keywords is omitted it is derived from the name or title filters; school or company filters alone are rejected with INVALID_INPUT, so include keywords with those. Company filters accept a company name, slug, numeric id, or URN; names are resolved for you. Costs 10 credits including the first 10 results; each further 10 results add 1 credit (limit max 30; keyless and trial callers max 10). A cursor page is a NEW call priced the same way by its own limit, so one limit=30 call is much cheaper than three limit=10 pages; prefer a larger limit over paginating. Do NOT combine a company NAME filter with limit=30: name resolution spends one of the call's three internal fetches, so that combination is rejected. With a company name keep limit<=20; for limit=30 pass the company's numeric id or URN (linkedin_get_company returns both). Returns name, position, location, urn, public_identifier per result, a cursor for the next page, and total_matches. Results with is_anonymous=true are private profiles; do not pass them to linkedin_get_profile. For one known person with a URL/slug, call linkedin_get_profile directly instead.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| title | No | ||
| cursor | No | ||
| school | No | ||
| keywords | No | ||
| freshness | No | ||
| last_name | No | ||
| first_name | No | ||
| max_credits | No | ||
| past_company | No | ||
| current_company | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| usage | Yes | |
| common | Yes | |
| entity | Yes | |
| platform | Yes | |
| freshness | Yes | |
| data_as_of | Yes | |
| canonical_url | Yes | |
| schema_version | Yes | |
| platform_fields | Yes |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!