Skip to main content
Glama
webdata-tools-mcp

webdata-tools-mcp

Get Instagram profiles, posts and comments

get_instagram_posts
Read-onlyIdempotent

Extract public Instagram profiles, posts, reels, captions, hashtags, likes, comments and media by username or post URL without login for creator research and brand monitoring.

Instructions

Public Instagram data from usernames or post links: profile details with followers, following, bio and links, latest posts and reels with caption, hashtags, mentions, likes, comment count, post time, images, video, carousel items, tagged users, location, audio and a pinned flag, and optionally the comments under each post. No login. Useful for creator research, brand monitoring and social listening. Runs the Apify Actor tacps126/instagram-scraper on your Apify account (about $0.0015 per profile or post, $0.0008 per comment; spend per call is capped at $0.5).

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

Input Schema

NameRequiredDescriptionDefault
profilesNoUsernames or profile links, e.g. ["nasa"].
max_itemsNoMaximum results to return (default 100, max 2000). Cost scales with this.
post_urlsNoPost or reel links, e.g. ["https://www.instagram.com/p/Dfc1mYxFevS/"].
extra_inputNoAdvanced: extra Actor input fields, merged over the defaults.
posted_afterNoOnly posts on or after this date (2026-11-01) or within a period ("7 days", "2 weeks", "1 month").
comments_per_postNoComments to read under each post (0 = none).
posts_per_profileNoLatest posts to read per profile (0 = profile only).

Output Schema

NameRequiredDescriptionDefault
toolYesName of the tool that produced the result.
countYesNumber of records the Actor returned.
itemsYesThe records. Long text fields are shortened to 600 characters.
shownYesNumber of records included in `items` (can be lower than count when the result is long).
truncatedYesTrue when records were left out to keep the result short; ask for fewer items.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.19.0

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is covered. The description goes well beyond that with real behavioral facts an agent could not get elsewhere: execution is delegated to a named Apify Actor on the caller's account, per-item pricing ($0.0015/profile or post, $0.0008/comment), and a hard $0.5 per-call spend cap, which directly informs batching decisions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

Purpose and pricing are front-loaded, but the middle of the description is a long field-by-field enumeration (caption, hashtags, mentions, likes, comment count, post time, images, video, carousel items, tagged users, location, audio, pinned flag) that duplicates the output schema and dilutes the operative information. Compressing that list would make the cost/auth/purpose statements far more salient.

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 zero-required-parameter, open-world scraper with an output schema, the definition covers what an agent most needs: source inputs, no-auth operation, cost model and spend ceiling. The remaining gap is operational combining logic — whether profiles and post_urls can be supplied together and how max_items, posts_per_profile and comments_per_post interact for cost planning.

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 every one of the seven parameters is already documented with types, defaults and bounds. The description adds only a light correspondence between 'optionally the comments under each post' and comments_per_post, and does not clarify how profiles vs post_urls interact or how max_items relates to posts_per_profile. Baseline 3 is appropriate when the schema does the heavy lifting.

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 names a specific verb and resource set ('Public Instagram data from usernames or post links') and enumerates the concrete artifacts returned: profile stats, posts, reels, and optionally comments. Instagram is a distinct platform from the siblings (get_threads_posts, get_facebook_pages, get_pinterest_pins), so an agent can route to it on platform alone 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 Guidelines4/5

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

It supplies clear usage contexts ('creator research, brand monitoring and social listening') and a prerequisite ('No login'), which tells the agent when the tool fits. It stops short of exclusions or naming alternatives, so there is no explicit when-not guidance, but the operational context is unambiguous.

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