Instagram Control MCP Server

instagram_unsave_post

Remove a post from your Instagram Saved collection by providing its media ID or URL.

Instructions

Remove a post from your Saved collection.

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_unsave_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.2/5.0

Behavior2/5

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

With no annotations and a terse description, the behavioral traits are not disclosed. There is no mention of error conditions (e.g., post not saved), side effects, or auth requirements. The description only restates the basic function without adding transparency beyond the obvious.

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, complete sentence with no unnecessary words. It front-loads the verb 'Remove', making the purpose immediately clear.

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 tool's simplicity (one parameter, straightforward action) and presence of an output schema, the description is minimally adequate for a basic understanding. However, it lacks details about error handling and output format, which are important for a complete tool definition.

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

Parameters2/5

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

The single parameter 'media_id_or_url' has no description in the schema (0% coverage). The tool description does not clarify the expected format (e.g., numeric ID or full URL) or provide examples. As the description fails to compensate for the schema's lack of detail, the score is low.

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 ('Remove') and the resource ('a post from your Saved collection'). It uses a specific verb and noun, making it unambiguous. It also distinguishes from sibling tools like 'instagram_save_post' which performs 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 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 vs alternatives such as 'instagram_delete_post' or prerequisites like the post being currently saved. The description does not include any contextual cues for appropriate usage.

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

Deploy Server