Skip to main content
Glama

instagram_click

Destructive

Clicks a freshly observed Instagram element to perform confirmed actions such as publishing, deleting, or changing content only when the user explicitly instructs it.

Instructions

Click a freshly observed element. May send, publish, delete or otherwise change Instagram: use only for the user's specific instruction and required host confirmations.

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": {
      "ref": "<ref>",
      "expected_account": "<expected_account>"
    },
    "name": "instagram_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYes
expected_accountYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and non-idempotency, and the description stays consistent while adding the specific consequences (send, publish, delete) and a confirmation requirement. What it omits is failure behavior for a stale or mismatched ref, which matters for a non-idempotent action.

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?

Two tight sentences, with the action and its consequence front-loaded before the usage restriction. No padding or repetition.

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 no explanation, and the danger profile is covered by annotations plus the description. The unexplained expected_account parameter is a genuine gap for a tool that can publish or delete.

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% and both parameters are required, so the description carries the full burden. 'Freshly observed element' hints that ref must come from a recent observation, but expected_account is never mentioned despite being a safety guard on a destructive operation.

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 a specific action (click) against a specific target class (an element observed in the current page state), which is enough to separate it from siblings that open pages, fill forms, or scroll. It stops short of clarifying how it differs from instagram_press, which an agent must infer.

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?

There is a real gating rule – only for the user's explicit instruction plus required host confirmations – which is meaningful for a destructive click. There is no guidance on how to obtain a valid ref (e.g., from a prior snapshot) or on when a sibling such as instagram_press would be the better call.

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