meta-mcp

List IG media (posts) of a Business account

ig_media_list

Retrieve a list of media posts from an Instagram Business or Creator account using a connected Facebook Page.

Instructions

GET /{ig_user_id}/media.

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": {
      "ig_user_id": "<ig_user_id>",
      "via_page_id": "<via_page_id>"
    },
    "name": "ig_media_list"
  }
}

Input Schema

Name	Required	Description	Default
`ig_user_id`	Yes
`via_page_id`	Yes
`fields`	No
`limit`	No
`auto_paginate`	No
`max_pages`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 10, 2026

TDQS

D1/5.0

Behavior1/5

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

With no annotations, the description must disclose behavioral traits. It does not indicate whether the operation is read-only, what the response format is, how pagination works, or any side effects. The existence of auto_paginate and max_pages parameters is not explained.

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

Conciseness1/5

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

The description is extremely short but fails to convey necessary information. It is under-specification, not conciseness. The single sentence does not earn its place as it provides no value beyond the endpoint.

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

Completeness1/5

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

Given 6 parameters (2 required), no output schema, and no annotations, the description is completely inadequate. It does not explain return values, pagination behavior, or any constraints, leaving the agent with no actionable understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description adds no meaning to any of the 6 parameters. The description does not mention parameter names or their roles, leaving the agent to infer nothing from the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description is merely the endpoint path 'GET /{ig_user_id}/media.' This is a tautology that adds no information beyond the tool name and title. It does not state what the tool does—it lacks a specific verb like 'list' or 'retrieve' and does not clarify that it returns media posts.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus alternatives (e.g., ig_media_get for a single media, ig_hashtag_media for hashtag-based search). The description does not mention prerequisites, context, or exclusions.

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