Skip to main content
Glama

list_recent_media

Read-onlyIdempotent

List the account's most recent posts and reels as they are on Instagram right now, newest first — including ones published straight from the Instagram app, which list_scheduled_posts (reeldrop's own queue) never shows.

limit is 1–50. Each row's ig_media_id is what create_automation / update_automation take as post_ids and what list_comments takes as media_id. Use it to find "my reel from last Friday" when the user did not post it through reeldrop. For live stories use list_live_stories; for how a post performed, get_reel_analytics.

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": {
      "workspace_id": "<workspace_id>",
      "ig_account_id": "<ig_account_id>"
    },
    "name": "list_recent_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
workspace_idYes
ig_account_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the description only needs incremental context, and it supplies it: the data is a live snapshot of the Instagram account rather than reeldrop's queue, and results are ordered newest first. It does not mention pagination or any account-permission requirements, which keeps 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.

Conciseness5/5

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

Front-loaded with the core behavior, then a constraint, then cross-references — every sentence carries distinct value (differentiation, limit bound, id handoff, alternatives). No filler or restatement of the name.

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?

With an output schema present, the description need not describe return values, and it still explains how ig_media_id feeds create_automation/update_automation/list_comments. The only gap is that the two required identifiers are never characterized, which for a low-complexity read tool is minor.

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 description coverage is 0%, so the description must compensate. It does document the limit range (1–50) and the meaning of the returned ig_media_id in downstream calls, but leaves workspace_id and ig_account_id entirely unexplained. Partial compensation for a low-coverage schema.

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 (list the account's recent posts and reels), plus scope qualifiers: live on Instagram right now, newest first, including posts made outside reeldrop. It explicitly contrasts with list_scheduled_posts, so an agent can distinguish it without opening the schema.

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?

Gives explicit routing rules: use this for content not published through reeldrop, use list_live_stories for stories, and get_reel_analytics for performance. It also provides a concrete scenario ('my reel from last Friday') that selects this tool over the scheduled queue.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources