Get LinkedIn Engagement Metrics
User asks specifically about LinkedIn engagement, social actions, lead generation metrics, or video performance.
Returns detailed LinkedIn engagement breakdown:
- Social engagement (likes, comments, shares, follows, reactions)
- Lead generation (one-click leads, form opens, completion rates)
- Video metrics (views, starts, completions, watch rates)
- Viral metrics (organic share impressions, clicks)
- Engagement rate calculations and benchmarks
Parameters:
- lookback_days: Number of days to analyze (7-120). Default: 30
- start_date: Optional start date (YYYY-MM-DD). Overrides lookback_days when used with end_date.
- end_date: Optional end date (YYYY-MM-DD). Overrides lookback_days when used with start_date. ⚠️ DATE CLARIFICATION: If the user’s date request is vague or ambiguous (e.g., “March to June” without a year, “last quarter”, “recently”, “a few months ago”), ask the user to specify exact dates before calling this tool. Do not assume or guess dates.
- ad_account_id: Required for multi-account users. Get from list_connected_accounts
Example Prompts:
- “Show me LinkedIn engagement metrics”
- “How many leads did we generate on LinkedIn?”
- “What’s our LinkedIn video completion rate?”
- “Are people sharing our LinkedIn ads?”
Execution time: 2-3 seconds
Authorizations
API key from https://adspirer.ai/keys. Prefix sk_live_. Treat as a secret — never commit.
Headers
Client-generated UUID to make writes idempotent. Strongly recommended for write tools. A repeat call with the same key returns the cached result instead of re-executing. Example: 550e8400-e29b-41d4-a716-446655440000
Body
All tool arguments are wrapped in an arguments object. The fields accepted inside arguments are listed below — required fields are marked with a red asterisk.
Input schema for getting LinkedIn engagement metrics breakdown
Response
Tool executed successfully. data.text carries the human-readable result (markdown-friendly). data.quota shows your current usage against the plan limit. data.structured appears when the tool emits machine-parseable structured content. data.content appears for tools that return non-text blocks (images, resources).
Returned on HTTP 200. data.text is the primary human-readable output. data.quota is always present for billable calls. data.structured is set only when the tool emits machine-parseable structured content. data.content is set only when the tool emits non-text content blocks.

