SimpleTexting MCP Server and API by Cotlet

List segments in SimpleTexting

simpletexting_list_segments

Read-onlyIdempotent

List segments in the user's own SimpleTexting account from ChatGPT, Claude or any AI agent. Returns how to do it in SimpleTexting step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's SimpleTexting Cloud Browser. SimpleTexting's official API: Yes, SimpleTexting has a REST API on any paid plan, but only on approval, and it has no official MCP server (checked 23 Oct 2026).

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": "simpletexting_list_segments"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Adds real behavior beyond the annotations: the tool returns procedural instructions and performs no action itself, which is the key thing an agent needs to know. It also notes the account scope (user's own account) and supplies API-availability context explaining why browser automation is required.

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 core two clauses (returns a step-by-step guide; do it with cotlet_browser_* tools) are front-loaded and useful, but the trailing API sentence, including the dated 'checked 23 Oct 2026' note, reads as boilerplate that dilutes focus without changing how the agent invokes the tool.

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?

With no parameters and no output schema, the description carries the return-value burden and does so: it says the output is a step-by-step guide with screens, buttons and fields. Combined with the explicit follow-up tool set, an agent has enough to chain this into a working flow.

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?

Zero parameters, so there is no parameter surface to mis-describe and the baseline of 4 applies. The description correctly implies no inputs are needed to produce the guide.

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

Purpose3/5

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

The name and first clause say 'List segments,' but the body reveals the tool actually returns a step-by-step how-to ('screens, buttons, fields') rather than segment data. That distinction is stated, but the mismatch between the verb 'list' and the real return means an agent has to read the whole description to know it gets instructions, not segments.

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?

Explicitly states the follow-up path: use the cotlet_browser_* tools in the user's SimpleTexting Cloud Browser to actually perform the steps. It also clarifies this tool 'opens nothing by itself,' which tells the agent it must pair this with browser tools. No exclusion against siblings is given, but the routing is clear.

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

All SimpleTexting MCP Server and API by Cotlet 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?