SimpleTexting MCP Server and API by Cotlet

List conversations in SimpleTexting

simpletexting_list_conversations

Read-onlyIdempotent

List conversations 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_conversations"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real behavioral value by stating it 'opens nothing by itself' and that the return is a step-by-step guide with screens, buttons and fields — information no annotation conveys.

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 purpose and the hand-off to browser tools are front-loaded, which is good. However, the trailing sentence about SimpleTexting's REST API and MCP server availability, complete with a dated parenthetical, is tangential to invoking this tool and dilutes an otherwise short description.

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 zero-parameter, read-only tool with no output schema, the definition covers what the call returns and what to do next. The only gap is that it does not describe the shape of the returned guide beyond 'screens, buttons, fields', which is minor at this complexity.

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?

The tool takes zero parameters, so the schema baseline is 4, and there is no parameter behavior left for the description to explain. Nothing in the description contradicts or obscures the empty input contract.

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 opening clause names a verb and resource ('List conversations in the user's own SimpleTexting account'), but the second sentence reframes the tool as returning a step-by-step how-to guide rather than conversation data. An agent can infer the intent, yet the name and the stated return value pull in different directions, leaving the actual purpose muddled.

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 description does give a workflow: get the instructions here, then perform the action with the cotlet_browser_* tools. It does not say when to prefer this over sibling conversation tools such as simpletexting_assign_conversation, nor does it state any prerequisites for the account being connected.

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?