Skip to main content
Glama
Instagram Campaign MCP

Instagram Campaign MCP

by enimarix

rank_posts

Read-only

Scores Instagram posts against your account's median engagement to identify winners for ad promotion, with optional filtering by performance tier and campaign.

Instructions

Score posts vs the account's own median (same type: feed/Reels/Stories), with baseline posts read at a similar age. engagement_index 1.0 = typical. A winner has enough reach (default 300) and either engagement >= the threshold (default 1.5x) or reach >= 2x the median with engagement >= 1.0x. Winners are the candidates to promote as ads. summary counts every post in scope, before the only filter.

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": "rank_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
onlyNo
limitNo
campaignNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely useful behavior beyond that: the median-comparison basis, matched baseline age, winner criteria (300 reach floor, 1.5x engagement or 2x reach with >=1.0x engagement), and the non-obvious fact that summary counts every post in scope before the `only` filter is applied. It does not disclose limit/pagination behavior or how posts lacking reach are treated.

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?

Dense but front-loaded: the scoring basis comes first, then the winner definition, then the summary caveat. Nearly every sentence carries information, with only minor cost from fragmented line breaks and the dangling 'before the `only` filter' clause.

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?

An output schema exists, so return values need not be spelled out, and the scoring model is well explained for a read-only analytic tool. The gap is on the input side: two of three parameters are undocumented in both schema and description, so an agent cannot know what `campaign` scopes or how `limit` interacts with the summary counts.

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

Parameters2/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 carry parameter meaning, and it largely does not: `limit` and `campaign` are never mentioned, and the `only` filter is named without explaining any of its ten enum values (e.g. too_early, no_baseline, inconclusive). The 300 and 1.5x defaults it cites are scoring thresholds, not parameters in the schema.

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?

States a specific operation (score posts against the account's own median) and defines the scoring unit precisely: same post type, baselines read at a similar age, engagement_index 1.0 = typical. That is enough to separate it from sibling insight tools like collect_insights or get_media_insights, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

It gives a clear outcome-based use case ('winners are the candidates to promote as ads') and defines the default winner criteria, which implies when to reach for this tool. However, there is no explicit when-not guidance and no routing to alternatives such as compare_variants or get_media_insights.

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