Skip to main content
Glama

instagram_login_finish

Closes the login browser and transfers the authenticated Instagram session state privately to Obscura, completing manual Playwright sign-in so browsing of posts, saved items, and Reels can begin.

Instructions

Close the login browser and transfer Instagram state privately to Obscura.

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_finish"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish that this is a non-read-only, non-idempotent, non-destructive operation. The description adds that it closes the browser and transfers state privately, but it does not explain failure behavior, whether the browser closes even if login failed, or what “state” includes; with annotations present, a 3 is appropriate.

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?

One front-loaded sentence with no redundant or filler text. It states the action and the privacy/transfer qualifier efficiently.

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?

The description covers the core action and annotations/output schema cover safety and return values. It still omits prerequisites and lifecycle context—when login is considered complete and how this differs from cancel/status—which leaves a gap for a terminal login step.

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 are no parameter semantics to document beyond the schema; baseline is 4. The description correctly avoids restating parameter details that do not exist.

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 names two concrete actions—closing the login browser and transferring Instagram state—so the tool’s purpose is clear. It does not explicitly contrast itself with instagram_login_cancel or instagram_login_start, which keeps it from a 5.

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

Usage Guidelines2/5

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

There is no guidance on when to call this versus instagram_login_cancel, instagram_login_start, or instagram_login_status. It implies a finishing step but does not state prerequisites such as a completed login or what to do if login failed.

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