search_connectors
Semantic search over the library. Describe the capability in natural language. Each result carriesslug, name, category, summary, setup and setupReason. Use the slug with attach_connector.
setup tells you what declaring it will leave behind:
This search returns the best matches only. Use
list_connectors when you need to know whether something exists at all.
list_connectors
Walks the whole library page by page, in a stable order. Returnstotal alongside the page, so you know when you are done. Use it to prove an app is absent, which a semantic search can never do.
list_agent_connectors
Lists the apps declared on a coworker with their real status and the tool names each one contributes. This is the truth, whatever the catalog predicted at search time. An app can be connected several times, one account each. Every row carries itskey, the bare slug for the first account and slug@id for the others, and the label that tells the accounts apart.
attach_connector
Declares an app on a coworker.Add another account of an app that supports several. Ignored for an app limited to one account.
status, the key of the account it declared, the available authMethods when one is still pending, and a message describing what is left to do.
Declaring an app on a coworker that will become a template is exactly the intended use. The person installing the template connects their own account.
detach_connector
Removes an app from a coworker: its tools, its credentials and the skill it installed.Account key from
list_agent_connectors, for example gmail@k3x9ab. Targets one account of an app connected several times.