Skip to main content
Glama

instagram_login_status

Read-onlyIdempotent

Verify that a manual Instagram login has established an active session before browsing posts, saved items, or Reels; returns status only without secrets.

Instructions

Check whether the manual login has reached an Instagram session; no secrets are returned.

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

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.8/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive, and the description adds genuinely new behavioral context: the check is against a manually-performed login and no secrets are returned in the response. What's missing is behavior for edge cases, e.g., whether it errors or returns a pending state before a session exists.

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?

A single compact sentence with the core purpose front-loaded and the safety clarification trailing it. Slightly telegraphic phrasing ("has reached an Instagram session") but no filler or redundancy.

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 parameterless status probe with an output schema covering return values and annotations covering the safety profile, the description supplies enough to call it correctly. The only real gap is enumerating the possible login states, which the output schema presumably carries.

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 nothing for the schema to document and nothing for the description to compensate for. The description correctly wastes no words on inputs.

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 and resource: "Check whether the manual login has reached an Instagram session." An agent can tell this apart from login_start/login_finish/cancel because it is explicitly a status check rather than a flow-control action. It does not name the siblings, but the purpose is unambiguous.

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 for polling or confirming the state of an in-progress login. There is no explicit guidance on when to call it versus instagram_login_finish or instagram_login_cancel, nor any note about polling cadence or terminal states.

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