get_account_summary_insights
Get comprehensive account details for specific domain(s).
Read analytics
What it does
Get comprehensive account details for specific domain(s).
USE FOR: Quick lookup of specific company information, engagement metrics, revenue data.
DO NOT USE FOR: Bulk analysis or complex filtering (use get_insights_report instead).
RETURNS: one entry per requested domain, in request order, each carrying its `domain`: engagement metrics (totalTouches, channels, websiteVisits), revenue data (openOppsAmount, closedWonOppsAmount), company info (name, industry, employees, engagementScore). A domain the platform could not answer comes back as {domain, error, data: []} in its own slot.Arguments
| Argument | Type | Notes | |
|---|---|---|---|
domains |
array | required | Domain strings. E.g., ['metadata.io'] |
Request
Request template, not a complete runnable example. Replace placeholders, empty objects, arrays, and zero values with valid account-specific inputs. Read required fields and nested constraints in the full schema. Confirm the account, connected channels, and referenced assets before calling a write tool.
curl -s -X POST https://mcp-server.metadata.io/mcp \
-H "Authorization: $METADATA_PAT" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "MCP-Protocol-Version: 2025-11-25" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_account_summary_insights","arguments":{"domains":[]}}}'Response
Recorded with these arguments. Enum values are the first the tool's own schema
declares; ids were fetched live from a list_ call immediately before.
{
"domains": [
"metadata.io"
]
}Recorded 2026-09-05 from the production server, in 567 ms. Values that identify a customer or disclose money are replaced with typed placeholders; keys, types and nesting are exactly as returned.
"[value redacted]"Related
Other analytics tools: