search_documentation
Search Tella’s help center, developer docs and website: how a feature works, where a setting is, what a plan includes. It runs the same search Tella’s in-app support assistant answers from. Your agent calls it before answering a question about how Tella works, and before offering to contact support about one.What to look up, as a question or a few words, such as
remove filler words or can viewers download my video. At most 300 characters.results, best match first, each with the page’s title, the section it’s under, its url and the matching text. An empty list means nothing matched.
submit_support_ticket
Send a request to Tella’s support team from the signed-in user. Your agent shows you the subject and message first and sends them only once you agree. Tella replies by email to your account’s address, and the ticket appears in your support inbox in Tella. Tella first searches its docs for the subject and message. When passages match, the call doesn’t send the ticket: it returns them, so your agent can answer you straight away. If they don’t help, the agent calls again with the sameidempotencyKey, subject and message and the docsToken it got back, and that call sends the ticket. A retry without the token shows the passages again rather than sending. Changing the subject or message searches again. When nothing matches, or the search can’t run, the first call sends the ticket, so it’s never a preview: the agent calls only once you’ve agreed to send.
The ticket always comes from the signed-in user: no parameter names another person, address or workspace. Your account’s email address has to be verified.
What you need: what you tried, what happened, what you expected, and the links of the videos involved. At most 4,900 characters.
true once you’ve seen the subject and message and agreed to send them. Any other value is refused.A key the agent makes up for this request, such as a UUID, and reuses on every retry of it. A retry with the same key returns the same ticket instead of opening a second one. At most 100 characters.
status: "docs_found" with the matching results (each with a title, section, url and text), a docsToken and a nextStep, or, once sent, status: "created" with the subject and replyTo, the address Tella replies to. Each user can send up to 5 new tickets an hour. A retry with the key of a ticket Tella already has returns that ticket, even past the limit.
submit_tool_feedback
Tell the team that builds Tella’s MCP tools about a problem with them: a tool that failed or gave a wrong result, a description or error that was unclear, a task that took too many calls, or something no tool can do. Your agent can call it on its own; it changes nothing in your workspace. It gets no reply: to get help, usesubmit_support_ticket.
Returns status: "received" and receivedAt once the team has it. Each user can send up to 20 reports an hour.