Instagram Control MCP Server

instagram_unarchive_post

Restore an archived post back to your Instagram profile grid by providing the media ID or URL.

Instructions

Unarchive a post (restores it to your profile grid).

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_unarchive_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

C2.8/5.0

Behavior2/5

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

Without annotations, the description should disclose behavioral traits. It mentions restoring to profile grid (indicating a mutation), but omits side effects, required permissions (post ownership), rate limits, or error conditions. For a state-changing tool, more transparency is needed.

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 a single concise, front-loaded sentence. It wastes no words, but additional detail (e.g., parameter info) would not harm conciseness significantly.

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 tool has one parameter, no annotations, and an output schema, the description is insufficient. It lacks parameter explanation, usage guidance, and sufficient behavioral transparency. Though the output schema may cover return values, critical execution context is missing.

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?

Schema coverage is 0%, yet the description does not explain the sole parameter 'media_id_or_url'. It adds no meaning beyond the name, leaving the agent uncertain about the required format (e.g., numeric ID vs full URL).

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 (unarchive) and resource (a post), with a clarifying parenthetical about restoring to the profile grid. It effectively distinguishes from the sibling tool 'instagram_archive_post' which performs the reverse operation.

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 is provided on when to use this tool versus alternatives (e.g., only for archived posts, prerequisites, or that it's the inverse of archive). The description does not mention usage context 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