Skip to main content
Glama
Sign In
instagram-mcp-server

instagram-mcp-server

by qaassimq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Send Direct Message

instagram_send_message

Send a text message to an Instagram user by recipient IGSID, within the 24-hour reply window or the 7-day HUMAN_AGENT allowance; public usernames will not work.

Instructions

Send a text message to an Instagram user.

Meta allows this only within 24 hours of that user's last message to the account. Outside the window, set tag="HUMAN_AGENT" to use the 7-day human-agent allowance; unsolicited messages are not possible at all.

Requires the messaging permission with Advanced Access. Get the recipient IGSID from instagram_list_conversations — a public username will not work.

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>",
      "text": "<text>"
    },
    "name": "instagram_send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoSet HUMAN_AGENT to reply up to 7 days out, when a human is handling the thread
textYesMessage text, up to 1000 characters
account_idNoSending account ID; omit for the token's own
recipient_idYesInstagram-scoped user ID (IGSID) of the recipient. Get it from instagram_list_conversations participants or from a messaging webhook — a public @username will not work.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare it as a non-destructive, non-idempotent, open-world write; the description adds policy-level behavior the annotations cannot express: the 24-hour messaging window, the 7-day human-agent allowance, the impossibility of cold outreach, and the Advanced Access permission requirement. That is exactly the kind of context that prevents failed or rejected 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?

Three tight paragraphs: what it does, the constraint and its escape hatch, then the prerequisite. The most consequential information (the 24-hour rule) is front-loaded and no sentence is redundant.

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?

Complete on the constraints that matter for a send operation — eligibility, permissions, recipient identifier format. With no output schema present, the description does not say what a successful send returns (e.g., a message ID), which is a minor remaining gap for chaining calls.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: it explains what the tag parameter is for in policy terms and warns that recipient_id must be an IGSID rather than a public username, which is the most common failure mode. account_id is left entirely to the schema, which is acceptable given its clear inline description.

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 — 'Send a text message to an Instagram user' — and the word 'text' implicitly separates it from instagram_send_media_message in the sibling list. An agent can identify the operation without opening the schema.

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

Usage Guidelines5/5

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

Explicitly defines the eligibility window (24 hours from the user's last message), the fallback path (tag="HUMAN_AGENT" for the 7-day human-agent allowance), and a hard exclusion ('unsolicited messages are not possible at all'). It also names the prerequisite tool, instagram_list_conversations, for obtaining the recipient ID.

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

Deploy Server

Other Tools