Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

instagram_reels_trending

Fetches Instagram's signed-out Reels feed currently shown on instagram.com/reels, returning post details such as shortcode, URLs, captions, dates, likes, comments, audio, and creator.

Instructions

instagram: Trending Reels. GET /v1/instagram/reels/trending. Get the reels Instagram's signed-out Reels feed (instagram.com/reels/) is showing right now, usually 8: shortcode, URL, caption, publication date (taken_at as ISO 8601, taken_at_timestamp in seconds), video and image URLs, like and comment counts, audio info and the creator. This is Instagram's own signed-out feed, not a ranked global chart, and repeated calls can overlap. Play counts are not in this feed: play_count 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

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": "instagram_reels_trending"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so well: it discloses the credit cost on success, that errors/blocked/timeout/invalid requests and cache hits are free, and the non-determinism of overlapping repeated calls. It also flags a missing field (play_count) that an agent might otherwise expect.

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?

The core is front-loaded and informative, but the tail devolves into generic pricing boilerplate ('A not-found or empty result is charged only where that operation's published cost says so') that adds no tool-specific value. The 'Play counts are not in this feed: play_count' fragment is also awkwardly spliced in.

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, so the description must describe returns, and it lists shortcode, URL, caption, ISO 8601 and epoch timestamps, media URLs, engagement counts, audio and creator. Combined with the cost and overlap caveats, an agent has everything needed to call and interpret this tool.

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?

The tool takes zero parameters, so the baseline is 4; the description correctly implies there is nothing to configure and instead spends its words on what comes back. No parameter meaning is needed or missing.

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?

States a specific verb and resource (get Instagram's signed-out Reels feed at instagram.com/reels/) and explicitly scopes it as 'not a ranked global chart,' which separates it from any notion of an algorithmic trending list. It also enumerates the returned fields, so an agent knows exactly what this call yields.

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 sets clear expectations for use: 'usually 8' items, 'repeated calls can overlap' (so it is not a deduplicated enumeration source), and play counts are absent so a consumer shouldn't call it for plays. It stops short of naming an alternative tool or stating an explicit do-not-use case, so it stops at 4.

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