Skip to main content
Glama

scroll_reels

Scroll the Instagram Reels default feed and extract structured metadata for each reel, including URL, creator, caption, likes, comments, and audio.

Instructions

Scroll the default Instagram Reels feed and return structured reel metadata.

Returns {reels: [...], count, timing, fill_rate}. Each reel: url, creator, caption, description (= caption), visual_description (IG auto alt-text), likes, comments, views, shares, reposts, date_posted (ISO 8601), date_posted_ts (unix), audio, _source. Engagement fields are best-effort — missing ones come back null rather than failing.

Note on views: the home feed omits view/play counts, so views is null here. Use search_reels/hashtag_reels for reels WITH view counts. See docs/views-investigation.md. shares and reposts are the same metric.

mode (optional): one of fast_test, normal_passive, conservative. Controls humanized delay/cap. Defaults to the server's configured mode.

This call drives the default feed only. For a topic use search_reels; for a tag use hashtag_reels.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNo
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Describes return structure, explains best-effort engagement fields and null views, clarifies shares/reposts equivalence, and details mode behavior. No contradictions with missing annotations.

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

Conciseness5/5

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

Efficiently organized with main purpose, return structure, caveats, mode explanation, and alternatives; no superfluous sentences.

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?

Covers all essential aspects: what it does, return format, parameter semantics, usage guidance, and edge cases; appropriate given output schema exists.

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?

Adds meaning for mode parameter (enum options and purpose) beyond schema; limit is self-explanatory but not expanded upon, which is acceptable.

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?

Clearly states the verb 'scroll' and resource 'default Instagram Reels feed'; distinguishes from sibling tools search_reels and hashtag_reels.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly says when to use this tool (default feed only) and when to use search_reels or hashtag_reels; also provides a note on views using alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Sho0pi/doomscroll-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server