Skip to main content
Glama

Switch Instagram account

switch_account
Idempotent

Makes another of the login's Instagram accounts the active one, for this connection. Use it before working on that account's posts and automations.

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": {
      "account": "<account>"
    },
    "name": "switch_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountYesAccount id or username from list_accounts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare the mutation profile: readOnlyHint=false, idempotentHint=true, destructiveHint=false. The description adds useful non-annotation context about scope ('for this connection'), which hints that the switch is per-connection rather than global. However, it does not say whether switching invalidates existing sessions, what happens if the account is already active, or what a failed switch returns — meaningful gaps for a state-changing call.

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 short sentences with zero filler; the core action and its scope are front-loaded, and the follow-on sentence carries the timing guidance. Nothing is redundant.

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 single-parameter, non-destructive state switch with annotations covering safety and idempotency and no output schema required, the description covers what it does, its scope, and when to invoke it. Only failure behavior and any side effects on existing sessions remain unstated, which is a minor omission.

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

Parameters3/5

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

Schema description coverage is 100%: the account parameter is documented as 'Account id or username from list_accounts', including accepted formats and the discovery tool to obtain values. The description adds no format, validation, or edge-case detail beyond that, so the schema does the heavy lifting.

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 states a specific verb+resource: it makes another of the login's Instagram accounts the active one, and it scopes that to 'this connection'. This clearly separates it from the read-only siblings like list_accounts or list_posts, which it does not name but whose role is implied via the account parameter.

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?

'Use it before working on that account's posts and automations' gives a concrete ordering condition for when to call it. It stops short of naming an alternative (e.g., that list_accounts supplies the id) or stating when not to call it, so it is clear context rather than full when/when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources