ClickSend MCP Server and API by Cotlet

Cancel scheduled SMS in ClickSend

clicksend_cancel_scheduled_sms

Read-onlyIdempotent

Cancel scheduled SMS in the user's own ClickSend account from ChatGPT, Claude or any AI agent. Returns how to do it in ClickSend step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's ClickSend Cloud Browser. ClickSend's official API: ClickSend has a full REST API and an official MCP server, but the MCP server is narrow (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": "clicksend_cancel_scheduled_sms"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description adds that it 'returns how to do it in ClickSend step by step (screens, buttons, fields) and opens nothing by itself,' which is valuable behavioral context beyond what the annotations convey.

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?

The description is front-loaded with the core action and then adds necessary context about the follow-up browser tools. The final sentence about ClickSend's official API being narrow is slightly tangential but still provides motivating context, so the description remains efficient overall.

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

Completeness5/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 description covers what it does, that it does not perform the cancellation itself, and how to actually carry out the cancellation. Nothing an agent needs in order to select and use this tool correctly is missing.

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?

With zero parameters, there is no parameter semantics to explain. The baseline of 4 applies because there is nothing for the description to compensate for and the schema is trivially complete.

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

Purpose5/5

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

The description states a specific verb (Cancel) and resource (scheduled SMS) and clarifies that it returns step-by-step instructions rather than performing the cancellation itself. It distinguishes this tool from actually doing the cancellation with cotlet_browser_* tools, making its role unambiguous among siblings.

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?

It tells the agent to use this tool to get step-by-step instructions and then to use cotlet_browser_* tools to carry out the cancellation. It also notes that ClickSend's official API/MCP server is narrow, explaining why this workaround exists. No explicit exclusions are given, but the intended usage path is clear.

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

All ClickSend 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?