Skip to main content
Glama

instagram_open

Read-onlyIdempotent

Opens an Instagram page or Direct view and returns the observed UI, enabling an assistant to inspect the page and perform follow-up actions.

Instructions

Open an Instagram page, including Direct; returns an observed UI for further actions.

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": {
      "url": "<url>"
    },
    "name": "instagram_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety is covered. The description adds the useful behavioral note that it returns an "observed UI" intended as a precondition for further actions, but says nothing about auth/login requirements or what happens if the URL is invalid or the page fails to load.

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?

One sentence, front-loaded with the action and resource, with no filler. The trailing clause about returning an observed UI earns its place, though "including Direct" is slightly ambiguous phrasing.

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?

Output schema exists, so return values need no explanation, and a one-parameter tool is inherently simple. Still, for a browser-navigation tool the description omits URL format and login-state preconditions, which are the main failure modes an agent would hit.

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 coverage is 0% for the single required parameter, so the description carries the full burden and does not meet it. "Including Direct" vaguely hints at supported destinations, but the accepted URL format (full profile URL vs. handle vs. Direct inbox URL) is never specified.

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 ("Open") and resource ("an Instagram page, including Direct"), so the agent knows this navigates rather than interacts. It does not name or differentiate itself from any sibling (e.g. instagram_click, instagram_scroll), leaving the boundary implicit.

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?

Usage is only implied by the phrase "for further actions" — an agent can infer this is a navigation step to run before interaction tools. There is no explicit when-to-use, no prerequisites (login state), and no named alternative for fetching page data without opening it.

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