Skip to main content
Glama
Instagram Campaign MCP

Instagram Campaign MCP

by enimarix

label_post

Associates an existing Instagram post with a campaign, variant, or hypothesis so it is included in compare_variants analysis.

Instructions

Attach campaign/variant/hypothesis to an existing post (e.g. one published from the app) so it counts in compare_variants.

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": {
      "media_id": "<media_id>"
    },
    "name": "label_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
variantNo
campaignNo
media_idYes
hypothesisNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare non-read-only, non-destructive, closed-world, so the safety profile is covered. The description adds the meaningful behavioral fact that labeling makes the post eligible for compare_variants, but says nothing about whether existing labels are overwritten, whether null clears a label, or whether the call is idempotent.

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?

A single front-loaded sentence stating action, inputs, and downstream effect with no filler. The trailing "so it counts in compare_variants" earns its place as the reason to call it.

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?

For a 4-parameter mutation with 0% schema coverage and an output schema present, the description covers purpose and effect adequately. It falls short on mutation semantics that an agent needs — overwrite vs. append behavior, clearing labels, and whether media_id must reference an already-published post.

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 0% schema description coverage, the description must carry parameter meaning, and it does map the three optional fields to campaign/variant/hypothesis plus imply media_id targets an existing post. It does not explain whether values must match an existing campaign name, whether null clears an existing label, or what media_id format is expected.

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?

The description pairs a specific verb ("Attach") with a specific resource (campaign/variant/hypothesis on an existing post) and names the downstream consumer, compare_variants. An agent can tell exactly what state change this produces and why, which no sibling tool does.

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 parenthetical "e.g. one published from the app" implies the tool is for posts created outside the publish pipeline, which is genuine when-to-use signal. However, there are no explicit exclusions, no statement about what happens if the post was already created by publish_* tools, and no alternative named.

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