Instagram Control MCP Server

instagram_archive_post

Archive an Instagram post to hide it from your profile grid while keeping it saved in your Archive section.

Instructions

Archive a post (hides it from your profile grid, but keeps it saved). Archived posts can be found in your Archive section.

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_archive_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.4/5.0

Behavior3/5

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

The description explains the behavioral effect (hiding from profile, keeping saved, accessible in archive) but does not mention authentication requirements, rate limits, or reversibility (though unarchive exists). Without annotations, it provides some transparency but has gaps.

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 two concise sentences with no fluff. It front-loads the core purpose and effect, making it easily scannable.

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 the simple tool (one param, output schema exists, no annotations), the description covers the basic behavior adequately. However, it lacks parameter documentation and explicit usage context, making it minimally viable but not fully complete.

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 required parameter 'media_id_or_url' with no description. The description does not explain what this parameter expects (e.g., ID or URL format). With 0% schema description coverage, the description should compensate but fails to add any meaning beyond the raw name.

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 ('archive'), the resource ('post'), and the effect ('hides it from your profile grid, but keeps it saved'). It also explains where archived posts are found. This distinguishes it from similar tools like delete_post or save_post.

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 implies usage when you want to hide a post without deleting, but it does not explicitly state when to use this tool versus alternatives like save_post or delete_post. In a large sibling list, explicit guidance would be helpful.

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

Deploy Server