Instagram Control MCP Server

instagram_create_highlight

Organize your Instagram stories by grouping them into a highlight collection with a custom title.

Instructions

Create a new story highlight collection from existing stories.

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": {
      "title": "<title>",
      "story_ids": "<story_ids>"
    },
    "name": "instagram_create_highlight"
  }
}

Input Schema

Name	Required	Description	Default
`title`	Yes
`story_ids`	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 provided, the description carries full burden. It states 'create' indicating a write operation, but fails to disclose any behavioral traits such as authentication requirements, limits on story IDs, or the effect of duplicate titles. This lack of detail is insufficient for a state-modifying action.

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, clear sentence that front-loads the core action. However, it is somewhat too brief, sacrificing important details for conciseness. Still, it avoids verbosity and is well-structured.

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 that this is a creation tool with two required parameters and no annotations, the description is incomplete. It does not mention return values (though output schema exists), prerequisites, or edge cases. For a tool that modifies state, more contextual information is needed.

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?

Schema description coverage is 0%, so the description must compensate. It mentions 'from existing stories' to hint that story_ids refer to existing stories, but provides no details on title constraints, format, or how to obtain valid story_ids. This is only slight context and does not add meaningful semantics.

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 verb 'Create' and the resource 'story highlight collection', and specifies the source 'from existing stories'. It effectively distinguishes this tool from siblings like 'instagram_get_highlights' or 'instagram_delete_highlight'.

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?

No explicit guidance on when to use this tool versus alternatives. It is implied that this tool is for creating highlights, but there is no mention of prerequisites or scenarios where other tools might be more appropriate.

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

Deploy Server