Interactive helpers

Editory’s in-app Studio chat and the MCP endpoint are the same tool registry. That’s the point — there’s one implementation and it can’t drift. The cost is that two tools which only mean something inside a chat window are also advertised over MCP.

You almost certainly don't want these

Both exist to draw UI. Over MCP they succeed and produce nothing your client can use. Your own client already has better ways to offer choices and accept files.

These are being withdrawn from MCP

Work is in flight to stop advertising the chat-only tools over MCP, on exactly the reasoning above. When it lands this page goes away — the docs build will say so, because the reference is generated from the registry and a page describing a tool that no longer exists fails the test suite.

suggest_quick_replies

Offer the user up to 4 short tappable reply options for your current question (e.g. "Source stock b-roll" / "Talking-head only"). Call at most once per reply, after asking the question. Purely a UI affordance — it does not answer for the user.

Parameter	Type	Description
options required	string[]

In the web app this renders tappable buttons under the assistant’s message. Over MCP it returns the options as data and draws nothing.

request_upload

Show the user an upload dropzone in the chat (e.g. for their own b-roll clips or an article file). The uploaded file URL arrives as an attachment on their next message.

Parameter	Type	Description
kind required	string	One of: broll, article_file.
prompt	string	Short label shown on the dropzone.

In the web app this opens a dropzone. Over MCP the result text says so, and points at the web app instead — because MCP has no file-transfer channel.

Getting your own footage in

Tools that take footage take URLs, not files:

{
  "script_id": "…",
  "broll_custom_files": [
    { "url": "https://…/clip.mp4", "name": "Harbour at dawn", "description": "Wide establishing shot" }
  ]
}

Anything reachable over HTTPS works. To use something on your own machine, upload it in the web app first — Editory keeps it in your asset library, and it becomes available by URL from then on.