Skip to main content
Glama
Instagram Campaign MCP

Instagram Campaign MCP

by enimarix

get_media_posts

Read-only

Retrieve recent Instagram posts newest first with type, caption, permalink, likes, and comments; use the next cursor as after to fetch older pages.

Instructions

Recent posts (newest first) with type, caption, permalink, likes, comments. Pass next_cursor as after for the next page.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_media_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNo
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuine value with the newest-first ordering and the per-item field list, but says nothing about rate limits, default page size, or what an empty result looks like. It neither contradicts nor richly extends the 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?

Two short sentences, zero filler, with the returned fields and ordering front-loaded and the pagination rule placed where it is needed. Nothing is redundant.

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?

The output schema and annotations cover return shape and safety, so the description need not restate those. However, for a paginated list tool it omits the semantics of `limit` and any indication of when this tool is the right choice among the many posting/insight siblings.

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 is the only source of parameter meaning. It does explain that `after` takes the next_cursor for the following page, but leaves `limit` (default 25) entirely unaddressed — no maximum, no effect on response size — so half the parameters remain unexplained.

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 names the resource (recent posts) and enumerates what each item carries (type, caption, permalink, likes, comments) plus the sort order, newest first. It is inferable that this lists content posts rather than analytics, but it never explicitly contrasts with siblings such as get_media_insights, so differentiation relies on the tool name.

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?

The only operational hint is pagination: 'Pass next_cursor as `after` for the next page.' There is no statement of when to choose this over get_media_insights, rank_posts, or get_comments, and no prerequisites or exclusions are given.

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