Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

instagram_search_popular

Fetches Instagram's public Popular page for a topic as a signed-out visitor, returning title, rounded reel count, topic summary, related search terms, and first 12 posts with creators and play counts.

Instructions

instagram: Popular Search. GET /v1/instagram/search/popular. Get Instagram's public Popular page for a topic (instagram.com/popular//), as a signed-out visitor sees it: the page title, its rounded reel count (total_media_count, as Instagram rounds it), Instagram's topic summary with sources, related search terms, and the first 12 posts with play counts and creators. The query is turned into the page's path ("best pizza in chicago" → /popular/best-pizza-in-chicago/). Ins Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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": {
      "query": "<query>"
    },
    "name": "instagram_search_popular"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesThe topic to look up, as words (best pizza in chicago) or as the page's slug (best-pizza-in-chicago)
cursorNoNot supported: only the first page is available signed out. Passing one returns 400.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the signed-out perspective, the fixed first-12-posts window, Instagram's rounding of total_media_count, that cursors return 400, and a detailed credit-cost policy including what is free. Auth mechanics and rate limits are left unstated, keeping 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?

Front-loaded with the endpoint and the resource, then payload contents, then cost policy – a sensible order. Slightly overstuffed with a garbled 'Ins Costs' fragment and a long, hedged pricing sentence, but no major filler.

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?

No output schema exists, and the description compensates by enumerating the returned fields (title, rounded reel count, topic summary with sources, related terms, first 12 posts with play counts and creators). Cost semantics are covered; error/response-shape details are only partially addressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% so the baseline is 3, but the description adds real meaning beyond the schema by showing the exact query-to-path normalization example ('best pizza in chicago' → /popular/best-pizza-in-chicago/). The cursor limitation is restated rather than newly explained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource – 'Get Instagram's public Popular page for a topic' – plus the underlying route, so an agent knows exactly what is returned. It is clearly distinct from keyword/hashtag search siblings by virtue of targeting the Popular page, though no sibling is named explicitly.

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?

Usage is implied by the resource definition (topic-based Popular page lookups) but there is no explicit when-to-use or when-not-to-use guidance, and no routing to alternatives such as instagram_reels_trending or tiktok_search_keyword. The signed-out / first-page-only constraint is the closest thing to a scope rule.

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

Deploy Server

Other Tools