These docs are an early preview — some sections are still being expanded.
Vidext Docs

Tool reference

Typed read and conversational tools exposed by the Vidext Operator MCP server.

The endpoint exposes these public tools. None of its public tool names contain _vidext_.

ToolAccessPurpose
search_knowledgeReadSearch connected knowledge available to the caller.
read_knowledge_sourceReadRead one accessible source returned by search.
list_modulesReadList modules visible to the caller.
get_module_statusReadInspect a module's authoritative outline and build status.
get_operationReadPoll an asynchronous operation by moduleId and operationId.
consult_operatorReadAsk the model to reason over a server-enforced read-only tool surface.
list_operator_chatsReadList up to 50 recent chats for the authenticated user and organization.
read_operator_chat_historyReadRead the bounded history of an accessible participant chat.
ask_operatorWriteStart or continue a write-capable operator conversation.

Conversational tools

consult_operator accepts a prompt but cannot mutate state: the server restricts the model to read-only tools. ask_operator can plan, build, and edit. It requires an idempotencyKey on every call so retries do not duplicate write-capable work. It can also accept a chatId, activeModuleId, and locale. Do not treat internal Operator tool names as callable MCP tools.

When ask_operator requests user input, relay the complete question and options, then continue the same chatId. Its response includes correlation IDs and, for asynchronous work, a typed next action:

{
  "tool": "get_operation",
  "arguments": { "moduleId": "018f1111-2222-7333-8444-555555555555", "operationId": "operation_..." },
  "pollAfterMs": 1500
}

Wait at least pollAfterMs, call get_operation with the supplied arguments, and repeat while its result has terminal: false. A nonterminal result supplies the next delay; a terminal planner result can supply the builder as nextAction, which you should follow.

Last updated on

On this page