Skip to main content
Glama

Preview a LinkedIn profile

preview_profile
Idempotent

[Acquire · free] Analyze a public LinkedIn profile or company page without a Flux account: pulls the latest ~50 posts (once per profile) and returns a teaser: post count, average engagement, the format that beats the baseline, the top post and the recent trend, plus a preview_id. The full breakdown (best day and hour, top and bottom posts with reasons, trends by format) and keyword search need a free Flux account: call preview_posting_insights or preview_search_posts with the preview_id, which asks the person to sign in where the client supports it, or give the person the continue_url if that call fails. Call claim_preview after sign-in only when the person says the profile is theirs.

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": "preview_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkedin_urlYesPublic LinkedIn profile or company URL, e.g. https://www.linkedin.com/in/janedoe

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is partly given. The description still adds real behavior: it pulls the latest ~50 posts once per profile (a caching/freshness constraint), returns a fixed teaser shape with a preview_id, and describes the sign-in prompt with a continue_url fallback if the auth call fails. That is strong context, though it does not explain the tension between readOnlyHint=false and what is actually written, nor any rate limits on repeated previews.

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?

Front-loaded with a bracketed cost/access tag and then purpose, tiers, and follow-up routing in a logical order. It is one dense paragraph with some run-on clauses (the sign-in/continue_url fallback sentence), but nearly every clause carries actionable routing information.

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?

For a single-parameter acquisition tool with no output schema, it covers return payload contents, the preview_id lifecycle, the account-gated follow-up calls, auth fallback behavior, and the claim_preview precondition. An agent has enough to call it and to handle the next two turns correctly.

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% and there is a single required linkedin_url already documented with an example. The description adds only the constraint that the URL must be public and may be a company page, which is marginal beyond the schema; 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?

States a concrete verb and resource: analyze a public LinkedIn profile or company page and return a teaser (post count, average engagement, best format, top post, trend, preview_id). It explicitly names the sibling tools preview_posting_insights and preview_search_posts as the deeper path, so it is separable from them without opening a schema.

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?

Gives explicit when-to-use (no Flux account, teaser-level analysis) versus when-not (full breakdown, keyword search require an account via the preview_* tools). It also states exactly when claim_preview applies: only after sign-in and only when the person says the profile is theirs.

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