Skip to main content
Glama

Instagram: Get paginated user followers

instagram_followers
Read-onlyIdempotent

List the followers of an Instagram account, with each follower's username, full name, profile picture and whether they are private or verified. Page through the list with cursor. Read-only: returns public data and changes nothing. Costs 1 credit per request.

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": {
      "username": "<username>",
      "count": "<count>"
    },
    "name": "instagram_followers"
  }
}

Input Schema

NameRequiredDescriptionDefault
countYesNumber of results to return (1–10). Defaults to 10.
cursorNoThe previous response's `nextCursor`, to fetch the next page. Omit it for the first page.
usernameYesInstagram username, or the profile link, e.g. "instagram" or "https://www.instagram.com/instagram/".
cacheOnlyNoReturn only a cached result and never scrape live. With `cacheMaxAgeHours`, only a result that recent is returned; without it, the latest cached result of any age. Responds 404, at no cost, when there is none, e.g. true.
cacheMaxAgeHoursNoAccept a cached result scraped up to this many hours ago. A cached result costs no credits, and its `cachedAt` says when it was scraped. When no cached result is that recent, the data is scraped live at the normal price. Leave it out to always scrape live, e.g. 24.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / cacheMaxAgeHours
      Added value: +{
      +  "description": "Accept a cached result scraped up to this many hours ago. A cached result costs no credits, and its `cachedAt` says when it was scraped. When no cached result is that recent, the data is scraped live at the normal price. Leave it out to always scrape live, e.g. 24.",
      +  "exclusiveMinimum": 0,
      +  "maximum": 9007199254740991,
      +  "type": "integer"
      +}
    • addedInput schema / properties / cacheOnly
      Added value: +{
      +  "description": "Return only a cached result and never scrape live. With `cacheMaxAgeHours`, only a result that recent is returned; without it, the latest cached result of any age. Responds 404, at no cost, when there is none, e.g. true.",
      +  "type": "boolean"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / username / description
      Previous value: -"Instagram username, or the profile link, e.g. \"instagram\" or \"https://www.instagram.com/instagram/\""New value: +"Instagram username, or the profile link, e.g. \"instagram\" or \"https://www.instagram.com/instagram/\"."
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds useful context beyond them: returned fields, cursor-based pagination, public-data scope, and a cost of 1 credit per request. It does not cover authentication requirements or private-account error behavior, so it falls 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with purpose and returned fields, then moves directly into pagination, safety, and cost. Every sentence carries useful information, and the slight overlap with the read-only annotation is mitigated by the added 'public data' detail.

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

Completeness4/5

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

For a paginated list tool with five parameters and no output schema, the description covers return fields, pagination, data scope, and credit cost. It omits edge-case behavior such as private or suspended accounts and does not mention the caching parameters, though those are fully documented in the schema.

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 schema already fully documents all five parameters, including count limits and the cache-related options. The description only reiterates cursor paging and does not add meaning beyond the schema, making the baseline 3 appropriate.

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?

The description states a specific verb and resource: 'List the followers of an Instagram account.' It also enumerates the returned fields, and the followers-vs-following distinction separates it from the sibling instagram_following without needing 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 Guidelines3/5

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

It gives a clear pagination instruction: page through the list with `cursor`. However, it does not explicitly say when to use this tool instead of instagram_user, instagram_following, or another platform's follower tool, nor does it state exclusions or prerequisites beyond the implication that only public data is returned.

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