Skip to main content
Glama

get_follower_history

Read-only

Daily follower counts for LinkedIn: one row per day (date, followers) for a profile or company page, the line behind a follower-growth chart. Answers "how have my followers grown day by day?", "follower count each day in March". The same numbers as the Analytics page's follower growth chart. Days before tracking started are left out and the start date is given; each series ends with the net change. With several LinkedIn channels and no account, returns one series per channel. LinkedIn only; for other platforms use get_analytics_summary.

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_follower_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodNoRolling window ending today. Default 30d. For any other window, pass start_date/end_date instead.
accountNoOptional. Which LinkedIn profile or page: its name or its id from list_connected_accounts. Omit for every LinkedIn channel on this workspace.
end_dateNoOptional. Last day of a custom range, YYYY-MM-DD, inclusive. Defaults to today. Needs start_date.
platformNoOptional, default linkedin. Daily follower history is LinkedIn only.
workspaceNoOptional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.
start_dateNoOptional. First day of a custom range, YYYY-MM-DD, in the user's timezone. Use for windows the presets don't cover: "last 14 days", "in March", "since Jan 1", "last year". Overrides `period`. Ranges can cover up to 366 days.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / workspace
      Added value: +{
      +  "description": "Optional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered and the description only needs to add behavior beyond that. It does: days before tracking started are omitted, the actual start date is returned in the payload, and each series ends with a net-change row — all non-obvious output-shape facts an agent would otherwise misread. Missing are any error/rate-limit or empty-result caveats (e.g. what happens if no tracking exists at all), which keeps it short of a 5.

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?

Purpose, return shape, gap handling, and the sibling boundary are front-loaded, and the layered example phrasings ('how have my followers grown day by day?', 'follower count each day in March') help an agent match user phrasing. It is on the long side for a read-only tool, and the two example questions plus the 'same numbers as the Analytics page' sentence repeat intent rather than adding new constraints.

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?

There is no output schema, and the description compensates by describing the returned rows, the omitted pre-tracking days, the returned start date, the trailing net-change entry, and the multi-series case. Combined with fully documented parameters and read-only annotations, nothing an agent needs to call and interpret this tool correctly is missing.

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%, including the period-vs-start_date override rule and the 366-day cap, so the schema already carries the heavy lifting and the baseline of 3 applies. The description's only additional parameter-adjacent information is the consequence of omitting `account` (one series per channel), which is more output semantics than input semantics, and it largely restates the schema's own note about omitting account for every LinkedIn channel.

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?

Names a specific verb+resource (daily follower counts / follower history), states the exact return shape (one row per day with date and followers) and the resource scope (profile or company page). It also draws a hard boundary against the sibling get_analytics_summary ('LinkedIn only; for other platforms use...'), so an agent can pick it out of a 60-tool list 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 Guidelines5/5

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

Explicitly marks the tool as LinkedIn-only and names the alternative for other platforms. It also gives the disambiguating condition for the sibling get_analytics_summary and covers the multi-channel case ('several LinkedIn channels and no account, returns one series per channel'), which is exactly the ambiguity an agent would otherwise resolve by trial and error.

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