Skip to main content
Glama
Sign In
instagram-mcp

instagram-mcp

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get operation

instagram_get_operation
Read-onlyIdempotent

Retrieve the status, preview, result, or error for an operation or approval by ID and reconcile unknown Instagram publish outcomes in one call.

Instructions

Look up one operation or approval by id (op_... or appr_...): status, preview, result or error. For unknown publish outcomes it reconciles against Instagram (one attempt per call) unless reconcile is false.

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": {
      "id": "<id>"
    },
    "name": "instagram_get_operation"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAn op_... or appr_... id.
reconcileNoTry to resolve an unknown outcome (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond the annotations: a lookup can trigger an outbound reconciliation against Instagram, that reconciliation is limited to one attempt per call, and it can be disabled with reconcile=false. The only gap is that it does not say what happens when reconciliation fails or the id is not found.

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 tight sentences with no waste. The primary lookup purpose is front-loaded and the conditional reconcile behavior follows immediately, which is the right ordering for an agent scanning the definition.

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 two-parameter lookup with no output schema, the description covers the essential surface: what is looked up, what comes back at a high level (status, preview, result or error), and the one non-obvious side effect. Missing detail about not-found or failed-reconciliation outcomes keeps it just below fully complete.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline would be 3, but the description adds meaning the schema does not carry: the id can be an operation id or an approval id, and reconciliation is a one-attempt-per-call network action rather than a passive flag. That extra semantics around reconcile (one attempt per call) is the main value added.

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 gives a specific verb (look up) and a precisely scoped resource (one operation or approval), and it names the id prefixes (op_... or appr_...) that identify each kind. The word 'one' implicitly separates it from instagram_list_operations, so an agent can distinguish the two without opening either schema.

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?

The description makes it clear that this tool is for looking up a single known id and that reconcile controls whether an unknown publish outcome is resolved against Instagram. It also states the default behavior (reconciliation happens unless reconcile is false), which is a real usage condition. It does not explicitly route the agent to instagram_list_operations for enumeration or to instagram_get_publish_status for the alternative path, so it stops short of full when-to-use/when-not guidance.

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