Skip to main content
Glama
Instagram Campaign MCP

Instagram Campaign MCP

by enimarix

send_dm

Reply to an Instagram DM within 24 hours of the user's last message by using the recipient ID from conversation history. The user must have messaged first.

Instructions

Reply to a DM (only within 24h of the user's last message; user must write first). recipient_id is the Instagram-scoped ID from get_conversation_messages.

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": {
      "recipient_id": "<recipient_id>",
      "message": "<message>"
    },
    "name": "send_dm"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYes
page_idNo
recipient_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare the safety profile (readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false), so the description's value is in the platform policy it adds: the 24-hour messaging window and the user-initiated-contact requirement. Those are genuinely non-obvious behavioral constraints not present in the structured data. However, it says nothing about failure modes when the window is closed, rate limits, or whether repeated sends are treated as distinct messages.

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?

Two compact sentences with zero filler. The hard constraint is front-loaded ahead of the identifier note, matching the order an agent needs the information in.

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?

An output schema exists, so return values need no explanation, and the critical policy gating for a DM send is covered. The remaining gap is the undocumented optional page_id and any expectation about how errors manifest when the 24-hour rule blocks a send. For a three-parameter action tool this is close to 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?

Schema description coverage is 0%, so the description carries the burden, and it does well for recipient_id by naming it as the Instagram-scoped ID obtained from get_conversation_messages — a meaning the bare schema cannot convey. The other two parameters are unaddressed: message format is not described, and page_id is an optional, defaulted-null field whose purpose and when-to-set condition are never explained. Compensation is therefore only partial across three parameters.

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 states a specific verb and resource ("Reply to a DM") and points at get_conversation_messages as the source of the required identifier, which lets an agent separate this write action from the read-side conversation tool. It stops short of explicitly contrasting with other messaging or comment tools, so the differentiation is helpful but not fully spelled out.

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 concrete preconditions: the reply must land within 24 hours of the user's last message and the user must have written first. That is real when/when-not guidance rather than implication. It does not say what to do when the window has expired (no fallback or alternative tool named), which keeps it off a 5.

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