Skip to main content
Glama
Instagram Campaign MCP

Instagram Campaign MCP

by enimarix

collect_insights

Snapshots insights for recent posts and live Stories into local storage, enabling campaign scoring with current metrics. Run daily; use stories_only for 20–24h Story snapshots.

Instructions

Snapshot insights of recent posts (and live Stories) into the local store. Run daily; scoring uses the latest snapshot of each post. Stories are only judged on a snapshot taken 20-24h after posting: the scheduler daemon takes those hourly, or call this with stories_only=True.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
max_age_daysNo
stories_onlyNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and openWorldHint=true; the description adds real behavioral context on top – that state is written to a local store, that scoring consumes the latest snapshot, and that Stories are only validly judged on a 20-24h snapshot. It does not disclose idempotency on repeat calls, API quota cost, or what happens when a Story snapshot window is missed, which are the remaining risks for a mutating collector.

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?

Three tight sentences, front-loaded with the action and destination, then the cadence, then the conditional Story rule. The scheduler-daemon clause is slightly dense but earns its place because it explains why a manual hourly call is normally unnecessary.

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 described, and annotations cover the safety profile. Still, for a collector with three defaulted parameters it never states which posts or accounts are in scope or how limit and max_age_days bound the work, which an agent needs to call it without guessing.

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 all three parameters and it only explains stories_only (via 'call this with stories_only=True'). 'Recent posts' faintly implies max_age_days and nothing at all explains limit or its default of 25, leaving two of three parameters with no meaning beyond their names.

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 a specific verb and resource: it snapshots insights for recent posts and live Stories into a local store, which is a materially different action from the sibling get_media_insights/get_account_insights readers. It stops short of explicitly naming a sibling to contrast with, so the agent must infer that this is the persistence path rather than the live-read path.

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

Usage Guidelines4/5

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

It gives a concrete cadence ('Run daily') plus a conditional branch for the Stories case, including the alternative mechanism (the scheduler daemon's hourly snapshots) and the escape hatch of calling with stories_only=True. There is no explicit when-not guidance, e.g. when a live read via get_media_insights is preferable, but the usage context is otherwise clear.

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