Skip to main content
Glama

instagram_press

Destructive

Presses a specified key on an observed Instagram element, including Enter to send or submit content.

Instructions

Press a bounded key on an observed element; Enter may send or submit content.

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>",
      "key": "<key>",
      "expected_account": "<expected_account>"
    },
    "name": "instagram_press"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes
refYes
expected_accountYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true and non-idempotent, and the clause "Enter may send or submit content" usefully corroborates that a keypress can commit a form submission. Beyond that, the description says nothing about what happens on failure, how expected_account is enforced, or which keys are permitted, so it adds only modest value over the structured hints.

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 side-effect warning placed last, which is a sensible ordering. Nothing is padded, though the brevity is partly under-specification rather than pure economy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, three-required-parameter action tool with no parameter documentation at all, the description does far too little: it omits the meaning of `ref` and `expected_account` and gives no guidance on valid key values or on what observation step must precede a press. An output schema exists, so return values need not be covered, but the invocation contract is incomplete.

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 description coverage is 0% with three required parameters, so the description is the only source of meaning — yet it only obliquely gestures at `key` and never explains `ref` (a selector/handle from observation) or `expected_account` (apparently a safety assertion about which account is active). The most consequential parameter is left entirely unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb ("press") and a target ("a bounded key on an observed element"), and the second clause hints at the Enter key's submit semantics. But "bounded key" is vague and nothing distinguishes this from sibling interaction tools like instagram_click or instagram_fill.

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 statement of when to use this versus instagram_click or instagram_fill, nor any prerequisite about the element first needing to be observed via a snapshot. Usage must be inferred entirely from the name and sibling list.

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