Skip to main content
Glama

LinkedIn Profile Posts

linkedin_profile_posts

[Acquire · 5 credits/page] Fetch recent posts from a LinkedIn person profile. 5 credits per page of 50, up to 250 posts, charged only for pages actually fetched. Results are stored in the post library (source_type='external') and linked to a linkedin_profiles row so profile-brief can render research-only prospects.

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": {
      "linkedin_url": "<linkedin_url>"
    },
    "name": "linkedin_profile_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
refreshNoBypass the cache and re-fetch from LinkedIn (5 credits per page of 50, charged only for pages actually fetched). Default false: a previously-fetched result is returned free, with how long ago it was retrieved.
max_postsNoMaximum posts to return (1-250). 5 credits per page of 50, charged only for pages actually fetched.
linkedin_urlYesLinkedIn profile URL (e.g. https://www.linkedin.com/in/username)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true), the description discloses the credit cost model, the 250-post ceiling, the 'charged only for pages actually fetched' rule, and the write side effect of storing results in the post library and linking them to a linkedin_profiles row. That side-effect disclosure is valuable and consistent with readOnlyHint=false. It stops short of covering failure modes or what a cached vs fresh response looks like.

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?

The credit tag is front-loaded, followed by purpose, cost, and storage consequences in a logical order. It is dense but each sentence carries information; the profile-brief/research-only-prospects clause is the most niche and borders on internal jargon.

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?

For a 3-parameter acquisition tool with no output schema, the description covers cost, pagination limits, caching, and downstream storage, which is nearly everything an agent needs. The main omission is any indication of what the call actually returns (post fields, handles, pagination tokens).

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 coverage is 100%, so all three parameters are already documented, including the refresh cache behavior and max_posts bounds. The description reinforces the credit-per-page economics tied to max_posts but adds no syntax or format detail beyond the schema, so 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?

The description opens with a specific verb and resource — 'Fetch recent posts from a LinkedIn person profile' — and the qualifier 'person profile' implicitly separates it from the company-profile sibling. An agent can identify the target entity and the returned data without opening the schema.

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 context is only implied: results feed the post library and 'profile-brief' for 'research-only prospects', which hints at the acquisition step but never states when to call this versus linkedin_company_posts, linkedin_profile_reactions, or search_posts. The cache-vs-refresh tradeoff is explained, but that is parameter behavior rather than tool selection guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources