keyapi-instagram-content-discovery

Explore and discover Instagram content at scale — search posts, Reels, hashtags, music, and locations to surface trends, audience signals, and content intelligence.

This skill enables deep content discovery on Instagram using the KeyAPI MCP service. It supports ID conversion between shortcodes and media IDs, detailed post inspection, comment and reply analysis, hashtag and music-based content search, Explore page browsing, and geo-targeted location discovery — all backed by real-time data.

Use this skill when you need to:

• Fetch full post details including engagement metrics, caption, and media data
• Analyze comments and nested replies for audience sentiment and topic signals
• Discover trending or niche content by hashtag, music track, or keyword
• Explore Instagram's Explore page to identify surfaced content categories
• Search for related hashtags, places, music, and Reels by keyword
• Identify content popularity signals for a specific song or audio track
• Perform geo-based location searches for hyper-local content research

author: KeyAPI license: MIT repository: https://github.com/EchoSell/keyapi-skills

Prerequisites

author: KeyAPI license: MIT repository: https://github.com/EchoSell/keyapi-skills

MCP Server Configuration

All tool calls in this skill target the KeyAPI Instagram MCP server:

Server URL : https://mcp.keyapi.ai/instagram/mcp
Auth Header: Authorization: Bearer $KEYAPI_TOKEN

Setup (one-time):

# 1. Install dependencies
npm install

# 2. Set your API token (get one free at https://keyapi.ai/)
export KEYAPI_TOKEN=your_token_here

# 3. List all available tools to verify the connection
node scripts/run.js --platform instagram --list-tools

author: KeyAPI license: MIT repository: https://github.com/EchoSell/keyapi-skills

Analysis Scenarios

Post & Comment Nodes

Explore & Hashtag Nodes

Search Nodes

author: KeyAPI license: MIT repository: https://github.com/EchoSell/keyapi-skills

Workflow

Step 1 — Identify the Discovery Objective and Select Nodes

Clarify the user's goal and map it to one or more nodes. Common research patterns:

• Post analysis: Resolve identifiers with convert_shortcode_to_media_id if needed → get_post_info → deepen with get_post_likes + get_post_comments.
• Comment thread analysis: get_post_comments → get_comment_replies for top comment threads.
• Hashtag content research: search_hashtags to discover relevant tags → get_posts_by_hashtag for content within each tag.
• Music content attribution: search_music to find a track → get_posts_using_specific_music with the returned music_id.
• Explore page research: get_explore_page_sections to list sections → get_posts_by_section to browse content in target sections.
• Geo-local discovery: search_locations_by_coordinates with latitude/longitude → search_places for city-level context.
• Reels keyword research: search_reels with keyword array → cross-reference with get_posts_by_hashtag for hashtag overlap.

Step 2 — Retrieve API Schema

Before calling any node, inspect its input schema to confirm required parameters, data types, and valid options:

node scripts/run.js --platform instagram --schema <tool_name>

# Examples
node scripts/run.js --platform instagram --schema get_post_comments
node scripts/run.js --platform instagram --schema search_reels

Step 3 — Call APIs and Cache Results Locally

Execute tool calls and persist responses to the local cache.

Calling a tool:

node scripts/run.js --platform instagram --tool <tool_name> \
  --params '<json_args>' --pretty

# Skip cache for fresh results
node scripts/run.js --platform instagram --tool <tool_name> \
  --params '<json_args>' --no-cache --pretty

Example — get post details:

node scripts/run.js --platform instagram --tool get_post_info \
  --params '{"code_or_url":"DRhvwVLAHAG"}' --pretty

Example — get comments (sorted by most popular):

node scripts/run.js --platform instagram --tool get_post_comments \
  --params '{"code_or_url":"DRhvwVLAHAG","sort_by":"popular"}' --pretty

Example — get replies to a specific comment:

node scripts/run.js --platform instagram --tool get_comment_replies \
  --params '{"code_or_url":"DRhvwVLAHAG","comment_id":"18067775592012345"}' --pretty

Example — get posts under a hashtag:

node scripts/run.js --platform instagram --tool get_posts_by_hashtag \
  --params '{"hashtag":"travel"}' --pretty

Example — search Reels (keyword as array):

node scripts/run.js --platform instagram --tool search_reels \
  --params '{"keyword":["fitness"]}' --pretty

Example — find posts using a music track:

# First: search for the music to get music_id
node scripts/run.js --platform instagram --tool search_music \
  --params '{"keyword":"happy"}' --pretty

# Then: get posts using that track
node scripts/run.js --platform instagram --tool get_posts_using_specific_music \
  --params '{"music_id":"564058920086577"}' --pretty

Pagination:

Instagram content endpoints use token- or cursor-based pagination — not numeric page numbers.

search_reels keyword type: The keyword parameter is a JSON array, not a plain string. Always pass it as an array: ["keyword"].

Explore page workflow:

# Step 1: list available sections
node scripts/run.js --platform instagram --tool get_explore_page_sections \
  --params '{}' --pretty

# Step 2: browse posts in a specific section (use section_id from Step 1)
node scripts/run.js --platform instagram --tool get_posts_by_section \
  --params '{"section_id":"10156104410190727","count":20}' --pretty

Cache directory structure:

.keyapi-cache/
└── YYYY-MM-DD/
    ├── convert_shortcode_to_media_id/
    │   └── {params_hash}.json
    ├── convert_media_id_to_shortcode/
    │   └── {params_hash}.json
    ├── get_post_info/
    │   └── {params_hash}.json
    ├── get_post_likes/
    │   └── {params_hash}.json
    ├── get_post_comments/
    │   └── {params_hash}.json
    ├── get_comment_replies/
    │   └── {params_hash}.json
    ├── get_explore_page_sections/
    │   └── {params_hash}.json
    ├── get_posts_by_section/
    │   └── {params_hash}.json
    ├── get_posts_by_hashtag/
    │   └── {params_hash}.json
    ├── get_posts_using_specific_music/
    │   └── {params_hash}.json
    ├── general_search/
    │   └── {params_hash}.json
    ├── search_hashtags/
    │   └── {params_hash}.json
    ├── search_places/
    │   └── {params_hash}.json
    ├── search_reels/
    │   └── {params_hash}.json
    ├── search_music/
    │   └── {params_hash}.json
    ├── search_locations_by_coordinates/
    │   └── {params_hash}.json
    └── get_cities_by_country/
        └── {params_hash}.json

Cache-first policy:

Before every API call, check whether a cached result already exists for the given parameters. If a valid cache file exists, load from disk and skip the API call.

Step 4 — Synthesize and Report Findings

After collecting all API responses, produce a structured content intelligence report:

For post analysis:

1. Post Overview — Shortcode, media type (photo/video/carousel), caption, publish date, like count, comment count, views (if video).
2. Engagement Analysis — Like-to-comment ratio, top commenters, sentiment signals from comment keywords.
3. Comment Thread Insights — Most replied-to comments, key discussion themes, brand or product mentions.
4. Audience Signals — Who is engaging, public account patterns where available.

For hashtag / topic research:

1. Hashtag Profile — Name, post volume, top recent posts.
2. Content Patterns — Common media types, caption styles, co-occurring hashtags.
3. Music Attribution — Tracks driving Reels content within the hashtag.
4. Opportunity Assessment — Saturation vs. engagement quality, optimal posting windows.

For music research:

1. Track Overview — Title, artist, music ID, total usage count.
2. Content Fit — Types of posts using this track, associated hashtags, creator tier distribution.
3. Trend Direction — Growth or decline in adoption by comparing page depths.

For location / geo research:

1. Location Index — Place names, IDs, coverage radius.
2. Local Content — Top posts geotagged to target area, thematic clusters.
3. City / Region Map — Available cities per country for campaign geo-targeting.

author: KeyAPI license: MIT repository: https://github.com/EchoSell/keyapi-skills

Common Rules

author: KeyAPI license: MIT repository: https://github.com/EchoSell/keyapi-skills

Error Handling