Instagram Control MCP Server

instagram_get_following

Retrieve accounts followed by the logged-in user or a specified username to analyze connections.

Instructions

Get the accounts that the logged-in account (or target username) is following.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "instagram_get_following"
  }
}

Input Schema

Name	Required	Description	Default
`username`	No
`amount`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 20, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It correctly identifies this as a read operation, but doesn't disclose behavioral traits such as pagination, rate limits, authentication requirements, or whether the 'amount' parameter limits results. Minimal but not misleading.

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 sentence with no unnecessary words, effectively communicating the tool's core function. It is front-loaded and concise.

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

Completeness3/5

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

Given that an output schema exists (but not provided) and the tool is simple (2 optional parameters), the description is adequate but not thorough. It does not mention pagination, error handling, or response structure, which would be helpful for a complete understanding.

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?

The description adds meaning to the 'username' parameter ('target username' vs 'logged-in account'), which is not clear from the schema alone. However, it does not explain the 'amount' parameter, leaving its meaning (likely maximum number of results to return) undocumented. Since schema coverage is 0%, the description partially compensates.

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?

The description uses a specific verb 'Get' and clearly identifies the resource as 'accounts that the logged-in account (or target username) is following'. It distinguishes this tool from the sibling `instagram_get_followers`, which retrieves followers instead.

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 explicit guidance on when to use this tool versus alternatives like `instagram_get_followers`. The description implies a read operation for following lists but doesn't specify prerequisites, exclusions, or provide context for choosing between this and other tools.

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

Deploy Server