Skip to main content
Glama
Instagram Campaign MCP

Instagram Campaign MCP

by enimarix

compare_variants

Read-only

Compare A/B campaign variants by their labels to see which performs better, and get flagged when the gap is too small or the sample too thin to call a winner.

Instructions

Compare A/B variants inside a campaign (by the variant labels given at publish/schedule time). Says when the gap is too small or the sample too thin.

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": {
      "campaign": "<campaign>"
    },
    "name": "compare_variants"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaignYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is free. The description adds real behavioral value beyond that: the result self-reports when the delta is not meaningful or the sample size is insufficient, which warns the agent not to over-interpret the output. It omits any mention of minimum sample thresholds or empty-result behavior, keeping it below a 5.

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?

Two sentences, front-loaded with purpose and followed by the output caveat. Slightly awkward anthropomorphism ('Says when...') for what is actually a flagged field in the response, but no filler or redundancy.

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

Completeness4/5

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

Output schema exists, so return values need no explanation; only one input is required and it is named. The definition covers what the tool does and the key interpretation caveat. A note on prerequisites (campaign must have published variants with labels) would make it complete.

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?

With one parameter and 0% schema description coverage, the description must carry weight. It clarifies that variants are not passed as parameters but derived from publish-time labels, which is genuinely useful semantics, yet it says nothing about the expected format or resolution of the 'campaign' argument beyond the field name.

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

Purpose5/5

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

States a specific verb and resource ('Compare A/B variants inside a campaign') plus the identity mechanism ('by the variant labels given at publish/schedule time'), which is precisely what separates it from insight-fetching or ranking siblings. An agent can tell this is a comparison tool, not a reporting tool.

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?

The scope 'inside a campaign' implies when to use it (you must already have published variants), and the label-based lookup implies a prerequisite. But it never states when to use this over e.g. get_media_insights or rank_posts, and gives no explicit exclusions or preconditions.

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