Skip to main content
Glama

instagram_fill

Destructive

Fills an observed Instagram comment, message, or caption input with specified text and checks the expected account, with Playwright handling authentication.

Instructions

Fill an observed comment/message/caption input; passwords and authentication use Playwright.

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>",
      "text": "<text>",
      "expected_account": "<expected_account>"
    },
    "name": "instagram_fill"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYes
textYes
expected_accountYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the risk profile is known. The description adds the security-relevant carve-out that credentials must go through Playwright, but does not state whether filling replaces existing text, triggers submission, or validates the account.

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 action front-loaded and the credential caveat appended; no wasted wording. It is efficient, though brevity here comes at the cost of the missing detail noted elsewhere.

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?

An output schema exists, so return values need no explanation, but a destructive, non-idempotent input-filling tool with three fully undocumented required parameters needs far more than one clause. The ambiguous expected_account in particular leaves an agent guessing at correct invocation.

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% across three required parameters, so the description must carry the load and largely does not. 'Observed ... input' loosely implies ref points at a previously observed element and text is the value, but expected_account is never explained despite sounding like a safety assertion.

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 verb 'Fill' and the target 'comment/message/caption input' give a recognizable intent, but 'observed ... input' is vague about what is being filled and how it relates to a ref. It does little to distinguish this from sibling interaction tools like instagram_press or instagram_click.

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 one explicit exclusion: passwords and authentication are handled via Playwright, which tells an agent when NOT to use this tool. However, nothing says when to prefer this over instagram_press/instagram_click, or what precondition (an observed element ref) must exist.

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