Skip to main content
Glama

instagram_login_start

Opens a separate visible browser window so you can sign in to Instagram and complete two-factor authentication manually, establishing the session needed for authenticated browsing.

Instructions

Open a separate visible browser for the user to enter Instagram login and 2FA.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "instagram_login_start"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

The description adds real context beyond annotations by disclosing that a separate, visible (non-headless) browser is opened and that a human must supply credentials and 2FA. However, it omits the behaviors that matter most here: whether the call blocks until the user finishes, what happens if the user abandons the flow, and how the session is handed off to the finish/status siblings. Annotations only say it is non-read-only, non-idempotent, and non-destructive.

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 sentence with no filler, and the key qualifier ('separate visible browser') is front-loaded before the purpose clause. Nothing could be removed without losing information.

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?

An output schema exists, so return values need not be explained, and there are no parameters to document. But for a stateful, human-in-the-loop tool, the description leaves out the surrounding workflow (finish/status/cancel) and the blocking semantics, which is the main gap an agent would need filled.

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?

The tool takes zero parameters, so there is no parameter meaning to convey and the baseline is 4. The description correctly implies no inputs are needed to launch the browser.

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?

The description uses a specific verb ('Open') with a concrete resource ('a separate visible browser') and states the intended user action (enter Instagram login and 2FA). It is clearly distinguishable from siblings like instagram_login_status, instagram_login_cancel, and instagram_login_finish, though it does not name them.

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: an agent can infer this is the entry point for an interactive login flow. It never states when not to call it (e.g. if a session already exists), nor that it belongs to a multi-step sequence with login_finish/login_status/login_cancel.

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