Skip to main content
Glama
Sign In
meta-mcp

meta-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ig_send_message

Sends an Instagram direct message to a recipient who has already messaged the professional account, using Facebook Login with the required Page and messaging permissions.

Instructions

Send an Instagram DM using Instagram Messaging with Facebook Login. Requires a Page access token, instagram_manage_messages, and pages_manage_metadata. The recipient must have messaged the professional account first.

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": "ig_send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesMessage text to send
recipient_idYesInstagram-scoped user ID of the recipient

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations present, the description carries the full disclosure burden and does meaningful work: it names the required Page access token and the instagram_manage_messages and pages_manage_metadata scopes, and flags the recipient-eligibility constraint. It omits response shape, rate limits, and failure behavior, keeping it below a 5.

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 short sentences, each doing distinct work: what it does, what credentials/scopes it needs, and the eligibility gate. The core action is front-loaded with zero filler.

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?

For a two-parameter send tool with no output schema, the description covers action, auth, scopes, and the critical recipient-eligibility rule. What is missing is modest: message text constraints and what a successful response returns.

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 both parameters are already documented and the baseline would be 3. The description earns the extra point by adding real semantics to recipient_id: the recipient must have an existing inbound message to the professional account, a constraint the schema does not express.

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 gives a specific verb and resource ("Send an Instagram DM") plus the API platform (Instagram Messaging with Facebook Login), which cleanly separates it from the read-side siblings ig_get_messages and ig_get_message. It does not name an alternative tool or scope boundary explicitly, so it stops just 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 Guidelines4/5

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

It states a hard precondition for use — the recipient must have messaged the professional account first — which is exactly the kind of usage gate an agent needs before attempting a send. It does not cover when not to use this versus other message-related tools or what to do when the precondition fails.

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