Fetch recent LinkedIn posts from a member's activity feed using their profile slug. Supports pagination with limit and offset for controlled retrieval.
Recent posts by a LinkedIn member (their activity feed), by profile slug.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Profile slug from linkedin.com/in/<slug>. | |
| limit | No | Results per page (1–50). | |
| offset | No | Offset into the captured results. |
Changes observed during successful MCP inspections.
v0.1.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full disclosure burden. It adds only the 'recent' temporal qualifier; it says nothing about pagination behavior (despite offset/limit params), rate limits, auth requirements, or what a returned post contains.
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?
A single short sentence with the resource and the identifying input front-loaded; the parenthetical clarifying 'activity feed' is the only addition and it earns its place. No filler.
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?
For a simple read tool with fully documented params this is minimally adequate, but with no annotations and no output schema the description leaves the response shape (what fields a 'post' includes) and pagination semantics entirely unexplained.
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?
Schema description coverage is 100%, so all three parameters are already documented in the schema, which sets the baseline at 3. The description's 'by profile slug' reinforces the required parameter but adds no format or constraint detail beyond the schema.
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?
States a specific verb ('get posts') and resource ('recent posts by a LinkedIn member / their activity feed'), scoped by profile slug. The 'member' qualifier implicitly separates it from linkfetch_get_company_posts, but no sibling is named explicitly, so it stops short of a 5.
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?
The phrase 'recent posts... activity feed' hints at the use case but gives no explicit when-to-use guidance, no exclusions, and no routing to alternatives such as linkfetch_search_posts or linkfetch_get_post. An agent must infer selection from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.