Agentio

List every Agentio API operation available on this account: one line per operation with its id, method/path, query parameters, and what it serves. Call this before your first call_api use to pick the right operation. This list, not the documentation, is the authority on what is retrievable: a topic absent from the docs may still have an operation here, and the docs can describe features this account cannot query. The list describes what this connection can retrieve, not the brand's complete account inventory. An omitted operation or a passing doc reference does not establish that a product feature is disabled for this brand. For a customer asking what data is available, describe the reporting measures in product language; ids and paths are tool-call arguments.

list_operations

Query the Agentio Brand API — Agentio's own first-party API for a brand's reporting data. Calls one of the read-only operations advertised by list_operations and returns the JSON response. Every call is automatically scoped to the brand's own data. Discover operations with `list_operations`, and read the operation's doc page (`api/<operation_id>.md` via read_product_doc) before the first call so parameters and response fields are used correctly. An empty result answers only exactly what you queried — never read it as proof the data doesn't exist elsewhere. Reporting rows show activity in the queried window, not current campaign status. Zero, null, and no rows are distinct; none alone diagnoses a tracking or ingestion fault. Interpretation: read this operation's cost definition, date basis, and denominator before choosing labels or aggregating. When a field represents full contracted cost, label it contracted cost in headlines and tables, not period spend or invoices. Check whether costs repeat across rows or windows before summing; different reporting families can use different cost bases. Use supplied rollups for totals and ratios. Read the operation's documented metric and missing-value meanings before interpreting a result or selecting a proxy. This tool supports rankings and explanations of recorded changes. Renewal, budget, pricing, and test-plan decisions belong with Ask Agentio in the Agentio dashboard after presenting the relevant numbers. Arguments: `operation_id`; `path_params` — object filling the {placeholders} in the operation's path (values must be UUIDs from earlier responses); `query_params` — object of documented query parameters (optional).

call_api

Read one Agentio product-documentation page by its bundle-relative path (e.g. 'index.md', 'connector/youtube/performance-reporting.md', 'api/<operation_id>.md'). Start from 'index.md' — it lists every page. These pages are the source for how the product works: what a metric means, how a workflow runs, what an operation's fields carry. Read the cost basis, date selection, eligibility rules, and null/zero meanings before interpreting a report. A documented possible explanation is not evidence that it occurred on this account. References to other operations do not grant access; list_operations defines what this connection can read.

read_product_doc

Search the Agentio product documentation. Matches the KEYWORDS in your query (not just an exact phrase) against each page's title, summary, and text, so a natural question finds the page that answers it even when the wording differs. Returns the best-matching pages, most relevant first, with a line of context each; follow up with read_product_doc on the relevant match before answering. A snippet is a lead, not a complete metric definition. No match means this search found no documentation, not that the product feature or the brand's data does not exist.

search_product_docs