Skip to main content
Glama
Sign In

Tulina

by ai.tulina.mcp
OverviewDiscussionsAdmin

instagram_act

Destructive

⚠️ SENDS a INSTAGRAM message via Unipile, from the person's own account — it leaves at once, there is no draft. Reading is instagram.

op:

  • "send" (default): sends text. chat_id → replies in an existing thread, 1-to-1 or group (from instagram(op="list")); otherwise recipient_id → opens a new thread with that contact.

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": {
      "text": "<text>"
    },
    "name": "instagram_act"
  }
}

Input Schema

NameRequiredDescriptionDefault
opNosend
_orgNoOrg (id) de CET APPEL. `oto_list_orgs()`.
textYes
_groupNoÉquipe (id) de CET APPEL, sous son org parente.
_run_idNoOBLIGATOIRE à chaque appel dès `run_start` ou `data_claim_next` : sans lui, l'écriture sur une ligne réservée est refusée. Hérité seulement si le serveur tient un run actif — n'y compte pas.
chat_idNo
_accountNoCompte à OPÉRER quand plusieurs existent. `oto_identity(op='list')`.
_projectNoProjet (id) de CET APPEL — jeton PRIMAIRE. `oto_project(op='list')`.
_instanceNoInstance de connecteur PRÉCISE (un credential exact). `oto_instance(op='list')`.
recipient_idNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, but the description adds the crucial detail that the message leaves at once with no draft, and that it is sent from the person's own account — which quantifies what the destructiveness actually means (an irreversible outbound message to a third party). It does not cover error handling or what happens when the account is not connected.

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?

The warning is front-loaded before the mechanics, and the bulleted op breakdown is easy to scan. Slight waste in explaining `op` as an option when it is a single-value const with the same default, which makes the bullet semi-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 ten-parameter, no-output-schema side-effecting tool with annotations present, the description covers the operation semantics, the reply-vs-new-thread branching, and the irreversibility warning. It stops short of naming prerequisites such as an active Unipile account or required _run_id/_org context for the write path, but those are surfaced in the schema.

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 schema leaves `text`, `chat_id`, and `recipient_id` as bare untyped strings with no descriptions, and the description compensates by explaining the mutually exclusive role of `chat_id` vs `recipient_id` and where chat_id comes from. The remaining system parameters (_org, _group, _run_id, _account, _project, _instance) are documented in the schema itself, so the 60% coverage gap is largely covered.

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

Purpose5/5

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

States a specific verb+resource (sends an Instagram message via Unipile, from the user's own account) and explicitly separates itself from the `instagram` sibling, which is the read path. An agent can tell the two apart without opening either schema.

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?

Explicitly routes reading to `instagram` and explains the two sending modes: `chat_id` replies in an existing thread, otherwise `recipient_id` opens a new one, with the source of chat_id (`instagram(op="list")`) named. No guidance on rate limits, account connection prerequisites, or failure cases, so it falls short of a full when/when-not treatment.

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

All Tulina toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources