Systeme.io MCP server for sales and pages

systeme_io_guide

Get guidance on navigating Systeme.io, signing in, and completing tasks such as building funnels, email campaigns, sales pages, and blog publishing. Call it first to plan work in a signed-in account.

Instructions

How to work in Systeme.io (funnels, email campaigns, sales and blog publishing): its screens and the sign-in link. Call this first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "systeme_io_guide"
  }
}

Input Schema

Name	Required	Description	Default
`task`	No	What you want done in Systeme.io, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Nov 14, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description must carry the behavioral load. It does disclose the informational content returned (screens, sign-in link) and implies a read-only orientation step, but never states that it performs no side effects, what form the guidance takes, or what an agent gains from the 'task' argument.

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

Conciseness5/5

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

Two short sentences with zero filler; the scope enumeration and the 'call this first' directive are both front-loaded and immediately actionable.

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 one-optional-parameter orientation tool with no output schema, the definition covers what the tool is, what it contains, and when to invoke it. Only the expected return shape and the role of the 'task' input remain unspecified.

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

Parameters3/5

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

There is a single optional parameter and schema coverage is 100%, so baseline is 3. The description does not add any meaning about how the free-form 'task' string is used or whether it is required for useful output.

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

Purpose4/5

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

Names a specific resource (guidance for Systeme.io) and enumerates the domains it covers: funnels, email campaigns, sales, blog publishing, plus screens and the sign-in link. This is distinguishable from the sibling browser-action tools (click/type/read/open), though the noun 'guide' rather than a verb leaves the operation slightly implicit.

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?

'Call this first' gives an explicit ordering directive that no sibling states, which is real usage guidance for orienting an agent before driving the UI. It does not, however, describe when the tool is unnecessary or what to do after calling it, so there is no exclusion or follow-up routing.

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

Deploy Server