Skip to main content
Glama
Sign In

Ignix

by social.ignix
OverviewDiscussionsAdmin

Learn a style from a public profile

import_style_from_link

Learn a writing (and, on Instagram, visual) style from a PUBLIC Instagram, TikTok or YouTube profile: the customer's own account that is not connected, or one they want to take inspiration from (the style keeps tone and form, never sentences). Ignix reads its latest 12 posts: their texts become style examples, and on Instagram its images give the colours and visual style (used for that pass and not kept). It learns the style itself at the end. Runs in the background for 1-2 minutes and returns a jobId for get_style_import_status. Costs 10 AI credits for Instagram and 120 for TikTok or YouTube; nothing is charged for a private or empty profile, or if the import fails. Tell the user the price before importing. SPENDS AI CREDITS ONLY WITH confirm: true. Call it first without confirm: nothing runs and nothing is charged, you get the quote (what it will do and the credits). Tell the user, in your own words, exactly that — including the options you chose, so they can change them — and wait for a clear yes before calling again with the same arguments and confirm: true. One yes covers the plan they approved (e.g. every line of an approved voice-over with the chosen voice); anything new or different needs a new yes.

Input Schema

NameRequiredDescriptionDefault
linkYesThe public profile, e.g. https://www.instagram.com/brand/, https://www.tiktok.com/@brand or https://www.youtube.com/@brand.
confirmNotrue ONLY after the user said yes to the quote (what it does and the credits). Without it nothing runs and nothing is charged.
accountIdNoAttach to (or read/delete from) ONE account. Omit for the workspace-wide style.
workspaceIdNoWorkspace to act in. Defaults to the workspace this connection is scoped to.
idempotencyKeyNoOptional. A unique id for this action (16-128 chars: letters, digits, _ : . -). If you are unsure whether a call went through (timeout, network error), repeat it with the SAME idempotencyKey and the same arguments: you get the original result and nothing is done twice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations cover only safety/cost flags, and the description adds substantial behavior: background execution for 1-2 minutes, a returned jobId consumed by get_style_import_status, credit costs (10 IG / 120 TikTok-YouTube), that images inform colour for one pass and are not kept, that style keeps tone and form but never sentences, and the confirm gate. This is exactly the extra context an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The critical information is front-loaded, but the confirmation flow is restated at least twice ('Tell the user the price before importing' then the full confirm paragraph again), and the closing example about an 'approved voice-over with the chosen voice' is copied from an unrelated tool and is actively confusing here.

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

Completeness5/5

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

With no output schema, the description still supplies the return contract (jobId plus the get_style_import_status handoff), timing expectations, cost model, and failure/no-charge conditions. Nothing essential for correct invocation is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning to 'confirm' and 'link': the first call must omit confirm to obtain a quote, and link must be a public profile with examples of valid URL shapes. accountId, workspaceId, and idempotencyKey are left to the schema.

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?

The description names a specific verb+resource (learn a writing/visual style from a public Instagram/TikTok/YouTube profile) and bounds it precisely: the profile must be PUBLIC and either unconnected or inspiration-only. It clearly differs from siblings like learn_brand_style or add_style_examples by scoping to a third-party public link and to the 12 latest posts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states when to use it (learning a style from a public profile, the customer's own unconnected account, or an inspiration account), when it is free (private/empty profile or failed import), and the exact confirm-then-call workflow with the instruction to quote the price first. Alternatives are implicitly handled by the profile-type scoping.

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

All Ignix 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