Tools
Tools are actions that an agent or workflow can perform. They can read data, search for information, create a record, send a message, analyze a file, or trigger work in another system.
Most tools come from Connections to external services. Some tools are System Tools, which are built-in Siesta AI capabilities assigned directly to agents. Custom API and MCP tools are configured by admins or developers.
Tool Types
| Type | What it is | Examples |
|---|---|---|
| Connection tools | Tools exposed through configured Connections. | Gmail, Jira, HubSpot, Google Drive, Google Ads |
| System Tools | Built-in Siesta AI/runtime capabilities assigned to agents. | Task Management, Grounding with Google Search, Web scraper, Code interpreter |
| Custom/API/MCP tools | Admin or developer-managed extensions. | REST API tools, MCP servers, internal services |
System Tools may not appear as ordinary user-created connections. See System Tools for the built-in capabilities and governance guidance.
When to Use a Tool
Use a tool when an agent needs to work with real data outside Siesta AI:
- read emails, calendar events, files, or CRM records,
- create a ticket, event, document, message, or business record,
- search for information through Google Search, Firecrawl, or an internal API,
- update items in advertising, analytics, or project systems.
If the agent should answer only from uploaded knowledge, use Data or Memory instead. If it should perform an action in another application, use a tool.
How to Work With Tools
- Open Connections and add the integration the tool needs.
- In the connection detail, check permissions, available functions, and whether write actions require approval.
- Add the connection to the agent, skill, or workflow where it should be available.
- In the prompt, describe what the agent should do with the tool and when it should ask for confirmation.
- Verify the result in the target application or in Tool Executions.
Reading vs. Changes
Some functions only read data, such as searching files, listing calendar events, or loading ticket details. Other functions change an external system: they create an event, send a Slack message, edit a campaign, or create a Jira issue.
For write actions, require confirmation wherever an unwanted execution could send a message, change data, publish content, or start a process outside Siesta AI.