Fresh Linkedin Profile Data MCP Server

Get Profile Latest Post Date

get_profile_latest_post_date

Retrieve the date of the most recent LinkedIn post for a profile by submitting its URL. This helps determine posting activity.

Instructions

Find out when he/she posted recently.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_profile_latest_post_date"
  }
}

Input Schema

Name	Required	Description	Default
`linkedin_url`	No	Example value: https://www.linkedin.com/in/ajjames/

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Sep 4, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. 'Find out' implies a read-only operation but doesn't disclose what happens for private profiles, what 'posted' includes, how the date is returned, or the behavior when there are no posts. Behavioral context is minimal.

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 description is very short and front-loaded, with no filler. It loses a point because the pronoun 'he/she' introduces unnecessary ambiguity and 'posted recently' is colloquial rather than precise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple, but with no output schema and no annotations, the description should clarify what exactly is returned (e.g., a date, timestamp, formatted string), whether the input is a LinkedIn profile URL, and any caveats around private profiles or missing posts. The current description is too thin to fully support correct invocation and interpretation.

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%, so the baseline is 3. The description does not explain the linkedin_url parameter beyond the schema, and the schema's description is only an example value rather than a semantic explanation, but no additional parameter guidance is required by the baseline. The description adds little meaning for the parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear goal: find the date of a profile's latest post. However, 'he/she' is vague and there is no differentiation from sibling tools like get_profiles_posts or detect_activity_time, so it stops short of a fully distinguishing definition.

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

Usage Guidelines2/5

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

The description implies a use case (checking how recently someone posted) but gives no explicit guidance on when to choose this tool over alternatives, no exclusions, and no mention of related sibling tools. With many similar post/profile tools listed, this is a notable gap.

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

Deploy Server