Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

instagram_user_reels

Fetch the first 12 public Instagram profile reels by handle, including play, like and comment counts, URLs, cover images and post dates; signed-out paging is unavailable.

Instructions

instagram: Reels. GET /v1/instagram/user/reels. Get the first 12 reels on a public profile's reels tab, each with play, like and comment counts, code, URL, cover image and date. Only the first 12 are available signed out: paging_info.max_id is always null and passing max_id returns 400. Captions are not on the reels tab; /v1/instagram/post has them. Requires handle: a lookup by user_id needs a login and returns 400. Post dates (taken_at, taken_at_timestamp, create 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_user_reels"
  }
}

Input Schema

NameRequiredDescriptionDefault
trimNoSet to true for a trimmed response.
handleNoThe Instagram username, with or without @ (required)
max_idNoNot supported: signed-out pagination is closed, so only the first 12 reels are returned. Passing one returns 400.
user_idNoNot supported: a lookup by user_id needs a login. Pass handle; user_id alone returns 400.
require_play_countsNoSet to true to fail (at 0 credits) instead of returning a reel without a play count.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/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 it well: it discloses the signed-out 12-item ceiling, the always-null paging_info.max_id, the 400 on max_id and user_id, and the credit model (1 credit on success; errors, blocked, timed-out, invalid and cache hits free). The one blemish is the garbled fragment 'Post dates (taken_at, taken_at_timestamp, create Costs 1 credit...', which appears truncated and leaves the date-field disclosure incomplete.

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 efficient, but the definition is long and ends with dense boilerplate about credits. The broken sentence starting 'Post dates (taken_at, taken_at_timestamp, create Costs 1 credit...' is a real structural defect that splices two thoughts together and hurts readability.

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?

For a read tool with no output schema and no annotations, this covers everything an agent needs: return fields, the 12-item signed-out cap, identifier requirements, failure modes, and cost behavior. Nothing essential for a correct call is missing, aside from the mangled date-field sentence.

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 coverage is 100%, and the description's parameter notes (handle required, max_id unsupported, user_id unsupported) largely restate what the schema properties already say. It does reinforce that handle is the only viable identifier, but it adds no format or syntax detail beyond the structured fields. Baseline 3 is 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?

States a specific verb and resource: 'Get the first 12 reels on a public profile's reels tab', and enumerates the returned fields (play, like, comment counts, code, URL, cover image, date). It also distinguishes itself from instagram_post by noting captions live there, not on the reels tab.

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?

Explicitly names the alternative for captions (/v1/instagram/post) and states hard constraints: only the first 12 are available signed out, max_id returns 400, and a lookup by user_id needs a login and returns 400. What it doesn't do is frame when to reach for instagram_user_reels versus instagram_reels_trending among the sibling set, but the constraint guidance is otherwise concrete.

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