Systeme.io MCP server for sales and pages

systeme_io_read

Reads the current Systeme.io page to extract text and numbered buttons, links, and fields, optionally within a specific element. Use it to inspect content before editing or acting.

Instructions

Read the current Systeme.io page: its text and numbered buttons, links and fields.

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

Input Schema

Name	Required	Description	Default
`element`	No	Read only inside this element.

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 whole burden, and it does disclose the shape of the returned content (text, numbered buttons, links, fields), which is genuinely useful. It says nothing about side effects, whether reads affect page state, size/truncation limits on large pages, or what happens when no page is open.

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?

A single tight sentence with the action and the returned content front-loaded and no filler. The colon-separated enumeration is efficient, though the sentence is slightly dense to parse.

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 read tool with no output schema, describing the returned payload is the key missing piece and it is present. The remaining gap is workflow context — how it fits with open/click/type — which a browser-automation agent would benefit from.

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?

Schema description coverage is 100%, so the schema already explains the optional `element` parameter and its 1-based minimum. The description never mentions scoped reads at all, so it adds nothing beyond the schema; 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?

The description gives a specific verb ("Read") and a specific resource ("the current Systeme.io page"), and enumerates what comes back: text, numbered buttons, links, and fields. It implicitly separates itself from navigation siblings by saying "current" page, but it never names or contrasts with systeme_io_open or systeme_io_status.

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?

There is no explicit statement of when to use this versus systeme_io_open, systeme_io_status, or systeme_io_guide; the reader must infer that this is the inspection step before clicking or typing. The word "numbered" hints at pairing with the click tool, but that relationship is never stated.

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

Deploy Server