analytics_digestPreview a client's daily analytics digest with spend, ROAS, top movers, alerts, and pending approvals to review performance and required actions.
Daily digest preview per client: spend, ROAS, movers, alerts, pending approvals (GET /v1/digest).
| Name | Required | Description | Default |
|---|---|---|---|
| date | No | ||
| clientId | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint=true and openWorldHint=true, so the safe-read profile is covered. The description adds that this is a preview and lists the sections included, but it does not disclose permissions, data freshness, rate limits, or whether alerts and approvals are returned as counts or full records.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The definition is a single front-loaded sentence with no filler beyond the endpoint reference. It is appropriately brief, though the endpoint suffix may be unnecessary for tool selection.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description lists the digest contents but is incomplete for correct invocation because it does not explain date/clientId behavior or output shape. With no output schema and 0% parameter documentation, more detail is needed for an agent to call it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must explain the two parameters. It only hints at clientId via 'per client' and never explains date syntax, defaults, or whether either parameter is optional.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The definition states a specific resource and scope: a daily digest preview per client, including spend, ROAS, movers, alerts, and pending approvals. This distinguishes it from generic analytics siblings like analytics_breakdown or analytics_timeseries, though it does not use an explicit retrieval verb.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus siblings such as alerts_list, approvals_list, reports_get, or other analytics endpoints. The word 'preview' hints at a preview use case, but the description never states when-not-to-use it or what alternative to choose.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.