Skip to main content
Glama
Sign In
instagram-mcp-server

instagram-mcp-server

by qaassimq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Mark Conversation Seen

instagram_mark_seen
Idempotent

Marks an Instagram conversation as read, clearing its unread badge so processed inbox messages are not treated as new. Use after handling messages to prevent duplicate reprocessing.

Instructions

Mark the conversation with a user as read, which clears its unread badge.

Use it after processing an inbox so the same messages are not reprocessed as new.

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": {
      "recipient_id": "<recipient_id>"
    },
    "name": "instagram_mark_seen"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idNoAccount ID; omit for the token's own
recipient_idYesInstagram-scoped user ID (IGSID) of the recipient. Get it from instagram_list_conversations participants or from a messaging webhook — a public @username will not work.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, idempotent, non-destructive operation; the description adds what actually changes (the unread badge is cleared) and the operational consequence (messages won't resurface as new). It doesn't cover edge cases such as marking an already-seen or nonexistent conversation, but the added effect-level context goes beyond the annotations.

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?

Two short sentences: the first defines the action and its effect, the second gives the usage rationale. Nothing is redundant and the key information is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter write tool with full schema coverage and annotations covering safety and idempotency, the description supplies the effect and the workflow motivation. Minor gaps remain around error cases and whether the read state is scoped per account, but nothing essential for correct invocation is missing.

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

Parameters3/5

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

Schema coverage is 100%, and the schema already explains that recipient_id must be an IGSID rather than a username. The description adds no parameter-level detail, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Mark the conversation with a user as read') plus the observable effect ('clears its unread badge'). It is clear what the tool does, but it does not explicitly distinguish itself from read-only siblings like instagram_get_conversation or instagram_list_conversations.

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

Usage Guidelines4/5

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

Gives a concrete triggering condition — 'Use it after processing an inbox so the same messages are not reprocessed as new' — which tells the agent both when to call it and why. No explicit when-not-to-use guidance or named alternative is provided.

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

Deploy Server

Other Tools