Read today's events; channel_pid required
| Name | Required | Description | Default |
|---|---|---|---|
| today | No | ||
| breakdown | No | ||
| event_name | Yes | ||
| channel_pid | Yes | ||
| product_ref | No | ||
| product_name | No |
| Name | Required | Description | Default |
|---|---|---|---|
| message | No | ||
| retryable | No | ||
| support_ref | No |
Changes observed during successful MCP inspections.
Input schema / properties / connection_contextRemoved value: -{
- "pattern": "^mctx_v1_[0-9a-f]{64}$",
- "type": "string"
-}Output schema / then / properties / categoryAdded value: +{
+ "type": "string"
+}Output schema / then / properties / expectedAdded value: +{
+ "type": "boolean"
+}Output schema / then / properties / failure_kindAdded value: +{
+ "type": "string"
+}Output schema / then / properties / responsibility_hintAdded value: +{
+ "type": "string"
+}Output schema / then / properties / routeAdded value: +{
+ "type": "string"
+}Output schema / then / properties / user_visibleAdded value: +{
+ "type": "boolean"
+}Input schema / properties / connection_contextAdded value: +{
+ "pattern": "^mctx_v1_[0-9a-f]{64}$",
+ "type": "string"
+}Output schema / $defs / s6Added value: +{
+ "properties": {
+ "can_report_stored_total": {
+ "type": "boolean"
+ },
+ "reason": {
+ "type": "string"
+ },
+ "zero_proven": {
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "can_report_stored_total",
+ "zero_proven",
+ "reason"
+ ],
+ "type": "object"
+}Output schema / else / properties / read_evidenceAdded value: +{
+ "description": "Proofs apply independently to returned metrics and scope as stored/observed. A new read_ref is a call identifier, never a source watermark. False or missing proof means unknown, not zero. Fingerprints correlate requests/results in audits; they are not authorization or pagination tokens.",
+ "properties": {
+ "artifact_returned": {
+ "type": "boolean"
+ },
+ "configuration": {
+ "properties": {
+ "account_inventory_enumerated": {
+ "const": false
+ },
+ "all_campaigns_paused_proven": {
+ "const": false
+ },
+ "requested_ids_complete": {
+ "type": "boolean"
+ },
+ "scope": {
+ "const": "requested_entity_ids_only"
+ }
+ },
+ "type": "object"
+ },
+ "mmp": {
+ "properties": {
+ "can_report_scoped_totals": {
+ "type": "boolean"
+ },
+ "provider_cache_max_age_seconds": {
+ "const": 90
+ },
+ "reason": {
+ "type": "string"
+ },
+ "scope": {
+ "const": "linked_apps_queried_channels_and_windows"
+ },
+ "source_observed_at": {
+ "type": "null"
+ }
+ },
+ "type": "object"
+ },
+ "read_ref": {
+ "pattern": "^read_[0-9a-f]{32}$",
+ "type": "string"
+ },
+ "request_fingerprint": {
+ "type": "string"
+ },
+ "result_fingerprint": {
+ "type": "string"
+ },
+ "scopes": {
+ "items": {
+ "properties": {
+ "all_campaigns_paused_proven": {
+ "const": false
+ },
+ "funnel": {
+ "additionalProperties": {
+ "$ref": "#/$defs/s6"
+ },
+ "maxProperties": 32,
+ "type": "object"
+ },
+ "index": {
+ "type": "integer"
+ },
+ "inventory_anchor": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "inventory_coverage": {
+ "type": "string"
+ },
+ "inventory_source_observed_at": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "metrics": {
+ "additionalProperties": {
+ "$ref": "#/$defs/s6"
+ },
+ "type": "object"
+ },
+ "metrics_source_observed_at": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "range_complete": {
+ "type": [
+ "boolean",
+ "null"
+ ]
+ },
+ "scope": {
+ "const": "stored_query"
+ }
+ },
+ "type": "object"
+ },
+ "maxItems": 10,
+ "type": "array"
+ }
+ },
+ "required": [
+ "read_ref",
+ "request_fingerprint",
+ "result_fingerprint"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered by structured data, and the description adds essentially nothing beyond it. It doesn't disclose whether today's data is live vs. partially aggregated, whether results are paginated or capped, or how 'today' is bounded.
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 short and front-loads the operation, with zero filler. However, that brevity comes at the cost of under-specification rather than being genuinely efficient – there is simply not enough content to justify the terseness.
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?
An output schema exists, so return values needn't be described, but a 6-parameter analytics query with 0% schema coverage needs far more than one sentence. The missing semantics of event_name, breakdown, and the product identifiers leave real ambiguity about how to invoke the tool 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% across 6 parameters, so the description carries the full burden and fails to meet it – only channel_pid is named, and that is already a required field in the schema. The required event_name and the optional today, breakdown, product_ref, and product_name are entirely unexplained, leaving format and interplay (e.g. product_ref vs product_name) unknown.
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?
States a verb and scope ("Read today's events") but the resource is only vaguely identified as "events" – the product/MMP dimension exists only in the tool name. It doesn't distinguish itself from the close siblings mmp_insights_query_product_event_summary or mmp_insights_get_product_today, so an agent cannot route confidently between them from the description alone.
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?
The only guidance is "channel_pid required," which restates a schema constraint rather than telling the agent when to pick this tool over the sibling MMP insight queries. There is no mention of when not to use it, prerequisites, or what 'today' means in terms of timezone/account context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.