Veezee

Overview Schema Related Servers Score Discussions

Get a LinkedIn person profile

linkedin_get_profile

Read-only

Retrieve a LinkedIn profile's overview and selected sections (about, experience, education, skills) using a profile URL, slug, or URN.

Instructions

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.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`sections`	No	Extra profile sections. First 2 are included in the base price.
`freshness`	No	recent (default) serves cached data from the last few hours when available; realtime forces a live fetch for +2 credits (refunded if we fall back to cached data). Trial keys are cached-only and reject realtime with TRIAL_CAP_EXCEEDED; paying upgrades this same key to unlock it.	recent
`identifier`	Yes	Profile URL, slug (after /in/), or urn:li:fsd_profile URN.
`max_credits`	No	Spend ceiling for this one call. The call is rejected (nothing charged) if its quote exceeds this. Only the quote is ever reserved, never this ceiling.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`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

A5/5.0

Behavior5/5

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

Discloses cost structure (base 4 credits, extra sections, realtime surcharge), caching behavior, trial key limitations, and spending ceiling. These details go well beyond the readOnlyHint and openWorldHint annotations. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Every sentence adds essential information, front-loaded with purpose and identifier details, then returns, costs, usage guidance. No redundancy or wasted words.

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?

Covers identifier, return overview, sections, costs, caching, limitations, and relationships to sibling tools. With a detailed output schema present, return value explanation is unnecessary. Complete for a tool of this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds significant explanation beyond schema: identifier formats and auto-cleaning, sections cost rules, freshness options with trial key behavior, and max_credits as a safety ceiling. Schema coverage is 100% but description enriches each parameter's meaning.

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?

Clearly states 'Fetch one person's LinkedIn profile' with specific identifier formats, distinguishes from linkedin_search_people and linkedin_get_company. Verb+resource is precise.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly guides to use linkedin_search_people for name-only queries, warns that anonymous search results cannot be fetched, and redirects company queries to linkedin_get_company. Provides clear when-to-use and when-not-to-use.

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

Install Server

Other Tools

Latest Blog Posts

Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly
Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
OpenAI
open source

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/veezeehq/veezee-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server