MCP limitations

The MCP tool set is a slice of the product, not all of it. Everything below is a fact about the current server, not a promise about a future one.

​

Scheduling is one-way

An assistant can create runs. It cannot undo them.

• No cancelling. There is no tool that cancels a pending or running execution.
• No deleting. A run scheduled by mistake stays until it runs, and has to be removed from the dashboard’s Schedule screen.
• No editing. A run’s time, device or inputs cannot be changed after the fact. Delete it in the dashboard and schedule a new one.

Cancelling and deleting do exist on the REST API — see Cancel execution and Delete execution. Editing a scheduled run exists nowhere.

​

Results are shallow

list_schedules reports a run’s status and, when it failed, the error recorded on it. It does not reach the artifacts.

• No logs. The step-by-step log, the error screenshot and the screen dump a failed run uploads are not exposed to any tool. An assistant cannot tell you why a run failed beyond the one-line error.
• No history beyond executions. Account follower history, and the dashboard’s aggregate stats, have no tool.

​

Whole areas have no tools

​

Results can be very large

There is no pagination anywhere. list_devices, list_accounts and list_media return the full set every time, and list_schedules caps at limit with no offset to page through the rest. On a fleet of a few dozen phones that is a lot of JSON, and it lands in the assistant’s context window in one piece. Narrow the request — filter list_schedules by device and date range, filter list_accounts by platform — rather than asking for everything and letting the assistant sort it out. list_media also strips file and thumbnail URLs, so an assistant can tell you what is in your library but cannot see it or hand you a link to it.

​

Scope is the key owner’s, not the organization’s

A connection acts as the person who approved it. Accounts, content, scripts and executions are limited to your own rows, even when you own the organization. Devices and tags are organization-wide but filtered by what you can reach. Full rules in What a key can see.

​

The wider API

The REST API covers most of what the tools do not: cancelling and deleting runs, collections, prompts, account pause and history, content starring and deletion, storage usage, and device tag and user assignment.