Skip to main content
Glama
Sign In
instagram-mcp

instagram-mcp

by lupikovoleg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_profile_publications

Retrieve a profile's main-grid publications, including reels, posts, and carousels. Filter by publication type, limit, and days back.

Instructions

Get main-grid profile publications, including reels, posts, and carousels.

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": {
      "target": "<target>"
    },
    "name": "get_profile_publications"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYes
limitNo
days_backNo
publication_typeNoall

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It states the tool retrieves data but does not disclose behavioral traits like authentication, rate limits, pagination, or side effects. Merely listing content types is minimal transparency.

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?

The description is a single sentence with no fluff. It is appropriately brief but could be slightly expanded to cover essentials without losing conciseness.

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

Completeness2/5

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

Given the complexity (4 parameters, many siblings) and presence of an output schema, the description is incomplete. It omits parameter explanations, usage context, and differentiation from similar tools.

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 offers no explanation for any of the 4 parameters (target, limit, days_back, publication_type). It adds no meaning beyond the schema's titles, failing to compensate.

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 specifies the resource ('main-grid profile publications') and includes types (reels, posts, carousels), which distinguishes it from siblings like get_profile_reels. However, 'main-grid' is not explicitly defined, slightly reducing clarity.

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 on when to use this tool vs alternatives. With many sibling tools (e.g., get_profile_pinned_publications, get_profile_reels), the description should indicate selection criteria but does not.

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