Skip to main content
Glama
Sign In
instagram-mcp

instagram-mcp

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Mark inbox items handled

instagram_mark_handled
Idempotent

Marks or unmarks inbox item IDs as handled in local bookkeeping so the inbox can hide them, without sending an Instagram request.

Instructions

Local bookkeeping: mark (or unmark) inbox item ids as handled so instagram_get_inbox hides them. No Instagram request.

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": {
      "item_ids": "<item_ids>"
    },
    "name": "instagram_mark_handled"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNoAccount alias; defaults to the configured default account.
handledNoDefault true; false unmarks.
item_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the description does not need to restate safety. It adds genuinely new behavioral context: the change is local bookkeeping only and issues 'No Instagram request', which no annotation expresses. It stops short of saying where that local state lives or how long it persists.

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?

A single front-loaded sentence labels the operation as local bookkeeping, states the action, and states the effect. No filler and no repetition of schema or annotation content.

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

Completeness5/5

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

For a three-parameter local-state toggle with no output schema and rich annotations, the description covers what it does, that it makes no network call, and what downstream tool is affected. Nothing an agent needs in order to invoke it correctly 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 67%, with account and handled already documented in the schema; the description's main contribution is clarifying that the id list targets inbox items and that the toggle can unmark. It adds little beyond that and says nothing about id format or the 100-item cap enforced by the schema.

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 names a specific verb (mark/unmark), a specific resource (inbox item ids), and explicitly distinguishes the effect from the sibling instagram_get_inbox, which it names. An agent can tell immediately that this is a local state toggle rather than a messaging action.

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?

It states the effect-driven use case (mark handled so instagram_get_inbox hides them) and implies the unmark path via 'or unmark'. There is no explicit when-not guidance or named alternative beyond get_inbox, but the usage context is unambiguous.

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