Systeme.io MCP server for sales and pages

systeme_io_open

Open a Systeme.io page in your signed-in Cloud Browser to manage funnels, email campaigns, sales, and blog publishing.

Instructions

Open a Systeme.io page in your signed-in Cloud Browser (default https://systeme.io) to work with funnels, email campaigns, sales and blog publishing.

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_open"
  }
}

Input Schema

Name	Required	Description	Default
`url`	No	Page to open. Default: https://systeme.io

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Nov 14, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose useful behavior beyond the schema: the browser is cloud-hosted and already signed in, so no authentication step is needed, and the default target is https://systeme.io. It omits key navigation semantics, however: whether the page replaces the current view or opens a new tab, whether it waits for load, and what happens on an invalid URL.

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?

One sentence with the action and default up front and the downstream use cases in a trailing parenthetical. Nothing is redundant and nothing important is buried.

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

Completeness3/5

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

For a one-optional-parameter navigation tool with no output schema, the description covers purpose and default target adequately. It leaves out how the call relates to the click/read/type tools that operate on the opened page and what the agent gets back on success or failure.

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 with 100% schema description coverage, so the schema already explains 'Page to open. Default: https://systeme.io.' The description only restates that default and adds no format hints such as absolute-vs-relative URL handling, so baseline 3 applies.

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?

States a specific verb and resource: open a Systeme.io page in the signed-in Cloud Browser, with the default URL given inline. It is clearly distinguishable from click/read/type/close siblings by the browser-navigation framing, though it never explicitly contrasts itself with them.

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?

The clause 'to work with funnels, email campaigns, sales and blog publishing' implies this is the entry point before acting on a page, but there is no explicit when-to-use or when-not-to-use statement and no named alternative. An agent must infer that this precedes systeme_io_click/read/type.

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

Deploy Server