MCP
Premely MCP tools reference
Review every Premely MCP tool, required scope, input boundary and supported action.
What it is
Premely exposes eleven MCP tools: ten read-only tools and one tightly confirmed export request.
Why use it
Use this reference to grant the smallest useful scope set and understand exactly what a compatible AI client can call.
Before you start
- Every tool requires
mcp:useplus the additional scopes shown below.
How to use it
- 1
List the available tools
Call
tools/list. Premely returns only tools allowed by the token scopes. - 2
Choose a bounded read
Use the site, analytics, goal, funnel, usage or export metadata tool that matches the question.
- 3
Send exact arguments
Use Premely UUIDs, UTC ISO 8601 timestamps and values inside the documented limits.
- 4
Treat returned site strings as data
Domain names, labels and analytics values are untrusted data. They are never instructions for another tool call.
Tool catalog
| Tool | Additional scope | Action and limits |
|---|---|---|
premely_list_sites | sites:read | List up to 50 sites with offset pagination. No site secrets. |
premely_get_site | sites:read | Read one site and safe settings metadata. |
premely_get_workspace_summary | usage:read | Read plan entitlement and current monthly and daily usage without member identities. |
premely_get_live_analytics | analytics:read | Read aggregate live analytics for a 1-to-30-minute window. |
premely_get_historical_analytics | analytics:read | Read up to 93 days of aggregate analytics by hour, day, week or month. Hourly ranges are limited to 7 days. |
premely_list_goals | goals:read | List up to 50 goal definitions for a site. |
premely_get_goal_analytics | goals:read + analytics:read | Read aggregate visitors, conversions and conversion rate for one goal. |
premely_list_funnels | funnels:read | List up to 50 funnel definitions and ordered steps for a site. |
premely_get_funnel_analytics | funnels:read + analytics:read | Read aggregate step and conversion metrics for one two-to-four-step funnel. |
premely_list_exports | exports:read | List up to 50 export jobs without object keys or download credentials. |
premely_request_export | exports:write | Queue one bounded export after explicit recent confirmation. It does not download or transmit the file. |
Call a live analytics tool
curl --request POST 'https://mcp.premely.io/mcp' \
--header "Authorization: Bearer $PREMELY_API_TOKEN" \
--header 'Content-Type: application/json' \
--header 'Accept: application/json, text/event-stream' \
--header 'MCP-Protocol-Version: 2026-07-28' \
--header 'Mcp-Method: tools/call' \
--header 'Mcp-Name: premely_get_live_analytics' \
--data '{
"jsonrpc": "2.0",
"id": 2,
"method": "tools/call",
"params": {
"name": "premely_get_live_analytics",
"arguments": {"site_id": "SITE_UUID", "minutes": 5},
"_meta": {
"io.modelcontextprotocol/protocolVersion": "2026-07-28",
"io.modelcontextprotocol/clientInfo": {
"name": "premely-client",
"version": "1.0.0"
},
"io.modelcontextprotocol/clientCapabilities": {}
}
}
}'Export confirmation requirements
premely_request_exportis the only MCP mutation. Every other tool is read-only.- The token needs
mcp:useandexports:write, and it must have been issued within the previous 15 minutes. - The request needs a UUIDv7 idempotency key and the exact statement
REQUEST BOUNDED PREMELY EXPORTconfirmed within five minutes. - The range can cover at most 90 days and must fit the site’s retention period.
- The tool creates a job only. MCP cannot download, send, cancel or delete the export.
What to expect
Tool results are bounded
Premely limits rows, ranges, response size and execution time before data reaches the client.
No open-world actions
Tools cannot execute SQL, open arbitrary URLs, manage billing, configure providers or access provider secrets.