Instagram Control MCP Server

instagram_pin_post

Pin a specific Instagram post to the top of your profile grid. Supports pinning up to three posts to organize your profile.

Instructions

Pin a post to the top of your profile grid. You can pin up to 3 posts on your profile.

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": {
      "media_id_or_url": "<media_id_or_url>"
    },
    "name": "instagram_pin_post"
  }
}

Input Schema

Name	Required	Description	Default
`media_id_or_url`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 20, 2026

TDQS

B3/5.0

Behavior2/5

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

The description only states the basic action and the 3-post limit. It does not disclose what happens if the limit is already reached, whether pinning replaces an existing pin, or any other behavioral traits beyond what is implied by the name.

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?

The description is two short sentences with no unnecessary text. However, it could be improved by adding parameter semantics without significantly increasing length.

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?

Given the presence of an output schema and only one parameter, the description lacks essential context about parameter usage and behavioral details, making it incomplete for an agent to use correctly.

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

Parameters1/5

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

The schema has one parameter ('media_id_or_url') with 0% description coverage, and the tool description does not explain what to provide. The agent has no guidance on how to specify the post to pin.

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 clearly states the action 'Pin a post to the top of your profile grid,' using a specific verb and resource. It distinguishes the tool from siblings like 'instagram_unpin_post' by implying the opposite action.

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

Usage Guidelines3/5

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

The description provides a constraint ('you can pin up to 3 posts on your profile') but offers no explicit guidance on when to use this tool versus alternatives like 'instagram_unpin_post' or when not to use it.

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

Deploy Server