Skip to main content
Glama
exileum

meta-mcp

ig_get_media_list

Retrieve a paginated list of media published on Instagram. Use limit, after, and before for pagination.

Instructions

Get list of media published on the Instagram account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of results (max 100, default 25)
afterNoPagination cursor for next page
beforeNoPagination cursor for previous page
Behavior2/5

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

No annotations provided, and the description only mentions 'published on the Instagram account,' which implies owner-only content but no details on pagination, rate limits, or potential mutability. Lacks depth.

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?

Very concise single sentence with no fluff. Could arguably include more structure (e.g., noting siblings or behavior), but remains effective and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a simple list tool with fully described parameters. However, lacks explanation of return format or media types (photos, videos), and no output schema exists. Minimal but not inadequate.

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?

Input schema has 100% description coverage for all three parameters (limit, after, before). The description adds no additional meaning beyond the schema, so baseline 3 applies.

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?

The description clearly states the tool retrieves a list of media, but does not differentiate from sibling tools like ig_get_media (single media) or ig_get_tagged_media (tagged media).

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives such as ig_get_media or ig_get_tagged_media. The user must infer from context.

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/exileum/meta-mcp'

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