Skip to main content
Glama
Instagram Campaign MCP

Instagram Campaign MCP

by enimarix

comment_on_media

Adds a comment from an Instagram account to one of its own posts, such as a pinned call to action.

Instructions

Add a comment from the account on one of its own posts (e.g. a pinned CTA).

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>",
      "message": "<message>"
    },
    "name": "comment_on_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYes
media_idYes

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 readOnlyHint=false, openWorldHint=true, and non-idempotent, so the safety profile is covered. The description adds one genuine behavioral constraint — the target must belong to the account itself — but says nothing about rate limits, public visibility, moderation, or what happens on duplicate calls.

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?

A single front-loaded sentence with the action first and a concrete example last. Nothing is redundant or padding.

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?

The tool is a simple two-parameter write with annotations covering its safety profile and an output schema covering return values, so the description needn't explain results. It is close to complete, though the thin parameter coverage leaves minor gaps around message formatting.

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 must compensate. It does partially: 'one of its own posts' clarifies media_id's ownership constraint, but there is no detail on ID format and no guidance on message content, length limits, or mention/hashtag handling.

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 uses a specific verb and resource ('Add a comment') and narrows the scope to the account's own posts, which implicitly separates it from reply_to_comment and get_comments. It never names a sibling outright, so it falls short of a 5.

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. a pinned CTA' gives one concrete use case, which is helpful context. There is no guidance on when to use this instead of reply_to_comment, and no preconditions or exclusions stated.

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