sprkly

Set up an automation

sprkly_create_automation_from_template

Set up one ready-made automation on one Instagram account and turn it on. This is the same as Go live in the app. It starts replying to real people right away, so show the user the template, the account, the word and the link first. Pass template_id from sprkly_list_automation_templates and profile_id from sprkly_list_profiles. If asks_for has post, pass post_id: a published Instagram post on that account. If it does not, leave post_id out. If asks_for has link, pass a full https link. keyword is optional and defaults to the template's word. message is optional and replaces the DM, or the public reply on a template that only replies in the comments. On first-comment-on-post, message is required: the comment sprkly adds under each new Instagram post it publishes on that account (up to 2,200 characters). That one is on Creator and Power, and an account can have one live. The coupon template is refused until message holds the real code instead of YOUR-CODE. If asks_for has faq, pass faq: 1 to 10 { keyword, answer } pairs. Each pair becomes its own automation that answers a DM of that word. fallback is optional there and becomes the account's default reply, for a DM with none of the words. It replaces any default reply already on that account, and turns it on if it was off, so tell the user first. A word another live automation already answers is refused. Calling again with the same list skips the words already live. Use sprkly_pause_automation to stop it.

Input Schema

Name	Required	Description
`faq`	No	Only when asks_for has faq. The words people DM you and the answer each one gets.
`link`	No	The https link the DM sends. Only when the template asks for a link.
`keyword`	No	The word people comment or send. Defaults to the template's word.
`message`	No	Your own words for the DM, for the public reply on a reply-only template, or for the comment on first-comment-on-post.
`post_id`	No	The published Instagram post to watch. Only when the template asks for a post.
`fallback`	No	Only with faq. The reply to a DM with none of the words. It replaces any default reply on the account and turns it on.
`profile_id`	Yes	The Instagram account to set it up on.
`template_id`	Yes	The template id from sprkly_list_automation_templates.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 23, 2026

addedInput schema / properties / fallback

Added value: +{
+  "description": "Only with faq. The reply to a DM with none of the words. It replaces any default reply on the account and turns it on.",
+  "type": "string"
+}

addedInput schema / properties / faq

Added value: +{
+  "description": "Only when asks_for has faq. The words people DM you and the answer each one gets.",
+  "items": {
+    "properties": {
+      "answer": {
+        "description": "The DM that goes back.",
+        "type": "string"
+      },
+      "keyword": {
+        "description": "The word they DM you.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "keyword",
+      "answer"
+    ],
+    "type": "object"
+  },
+  "maxItems": 10,
+  "minItems": 1,
+  "type": "array"
+}

changedInput schema / properties / message / description

Previous value: -"Your own words for the DM, or for the public reply on a reply-only template."New value: +"Your own words for the DM, for the public reply on a reply-only template, or for the comment on first-comment-on-post."

AddedOct 21, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Goes well beyond annotations: discloses it goes live immediately and replies to real people, warns of destructive-ish overwrite (fallback replaces any default reply and turns it on, so tell the user first), documents plan gating (Creator/Power, one live per account), refusal conditions (coupon template, already-live word), and re-call behavior (same list skips already-live words).

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?

Front-loaded with the core action and the confirmation step, and every sentence carries information. It is dense and run-on in places (faq/fallback clauses), costing a bit of parseability, but no sentence is wasted.

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?

For an 8-parameter mutation tool with no output schema, the description covers activation effects, conditional parameter rules, plan limits, refusal/skip behavior, and the stop-tool handoff. Nothing an agent needs to invoke it safely is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage the baseline is 3, but the description adds genuine conditional semantics: post_id only when asks_for has post, link must be https, keyword defaults to the template's word, message required and highlighted on first-comment-on-post, faq triggers one automation per {keyword,answer} pair, fallback behavior. This is meaning the schema alone doesn't convey.

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 and resource ('Set up one ready-made automation on one Instagram account and turn it on') and clearly differentiates from siblings by naming sprkly_list_automation_templates, sprkly_list_profiles, and sprkly_pause_automation. An agent can tell exactly what this does versus list-templates or pause-automation.

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?

Explicitly routes the prerequisites (template_id from sprkly_list_automation_templates, profile_id from sprkly_list_profiles), says to show the user the template/account/word/link first, gives conditional branching on asks_for (post/link/faq), and names sprkly_pause_automation as the stop path. This is a full when/how/alternatives map.

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

All sprkly tools Inspect

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

Need Help?