MCP
Tools
How the tools are shaped, and the two that are not collections.
Most tools are list_* — one per collection, listed on the
overview. They take the same arguments, because they are the same
API endpoints underneath:
| Argument | Meaning |
|---|---|
limit | Records per page, 1–50, default 20. |
offset | Records to skip. |
search | Free-text match over the record's main fields. |
sortBy, sortOrder | Field and direction; an unknown field falls back to newest first. |
createdAfter, createdBefore, updatedAfter | ISO 8601 timestamps. |
locationId | Which location to read, on the tools that belong to one. |
Two tools are not collections:
whoami— the company, the acting employee, the granted scopes, and the tools they unlock. Worth calling first in a conversation.get_api_resource— one record, or any API path with no tool of its own:{ "path": "customers/<id>" },{ "path": "settings/company" }. It goes through the same scope checks as everything else, so it can't reach past the token.
Results come back summarised — the fields that identify a record, not every
column — with a line above the data saying how many of how many you're looking
at and how to page further. Use get_api_resource when you need a full record.