subscribe

instagram-mcp

Overview Schema Source Related Servers Discussions Admin

Subscribe to an Instagram thread to receive its events. Assign a short alias for easy reference; only subscribed chats deliver events.

Instructions

Subscribe to an Instagram thread and give it a short alias.

This is the ONE place a raw thread id is entered (from list_threads or search_threads). Only subscribed chats deliver events.

Args: chat_id: Thread id, e.g. '340282366841700000000000000000000000001'. alias: Short memorable handle (e.g. 'alex'). Derived from the thread title if omitted.

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": {
      "chat_id": "<chat_id>"
    },
    "name": "subscribe"
  }
}

Input Schema

Name	Required	Description	Default
`alias`	No
`chat_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 7, 2026

TDQS

A4.1/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose two useful traits: that only subscribed chats deliver events, and that this is the sole entry point for raw thread ids. However, it omits idempotency (does re-subscribing error or overwrite?), permission requirements, and what happens to an existing alias on conflict.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the purpose, then the key scoping rule, then a structured Args block. Efficient and skimmable, with only minor redundancy between the alias definitions.

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 not be described. For a two-parameter mutation tool the description covers purpose, sourcing of ids, the alias fallback, and the side effect of subscribing; only edge-case behavior (re-subscribe, alias collision) is missing.

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 description coverage is 0%, so the description must compensate, and it largely does: chat_id is explained with a concrete example value, and alias is defined semantically plus given a fallback rule ('Derived from the thread title if omitted').

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 (Subscribe) and resource (Instagram thread), plus a secondary effect (assign a short alias). It also explicitly positions itself as 'the ONE place a raw thread id is entered', which distinguishes it from list_threads/search_threads and the other 25 siblings.

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?

Gives clear context for when this matters ('Only subscribed chats deliver events') and names where chat_id comes from (list_threads or search_threads). It stops short of explicitly contrasting with unsubscribe/list_subscriptions or stating exclusions.

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