Skip to main content
Glama
Sign In
Instagram MCP Server

Instagram MCP Server

by osborn1997
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

send_message

Send text or media messages to Instagram or Facebook Messenger users using their platform APIs.

Instructions

Send a message to a user on Instagram or Facebook Messenger. Can send text or media (image, video, audio).

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": {
      "platform": "<platform>",
      "recipientId": "<recipientId>"
    },
    "name": "send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformYesPlatform to send message on
recipientIdYesThe user ID to send the message to
textNoText message content (optional if sending media)
mediaUrlNoURL of media to send (optional)
mediaTypeNoType of media being sent
isHumanAgentNoSet to true if message is from human agent (extends messaging window)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It states the tool sends messages but doesn't disclose behavioral traits like authentication requirements, rate limits, whether messages are reversible, delivery confirmation, or error handling. This is inadequate for a mutation tool.

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?

The description is a single, efficient sentence that front-loads the core purpose and key capabilities. Every word earns its place with no redundancy or unnecessary details.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description is incomplete. It lacks information about behavioral aspects like permissions, side effects, response format, and error conditions, which are critical for proper usage.

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 100%, so the schema fully documents all 6 parameters. The description adds minimal value by mentioning platforms and media types, which are already covered by the schema's enum and descriptions. Baseline 3 is appropriate as the schema does the heavy lifting.

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 clearly states the action ('send a message'), target ('to a user'), platforms ('Instagram or Facebook Messenger'), and content types ('text or media'). It distinguishes from read-only sibling tools like get_conversation_messages, but doesn't explicitly differentiate from send_reaction or reply_to_comment.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like send_reaction or reply_to_comment. It mentions platforms and content types but doesn't provide context about appropriate scenarios, prerequisites, or exclusions.

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