Ledger-backed insights overview for up to 20 scopes. Use server summaries instead of summing visible rows.
| Name | Required | Description | Default |
|---|---|---|---|
| scopes | Yes | ||
| connection_context | No |
| Name | Required | Description | Default |
|---|---|---|---|
| ok | No | ||
| code | No | ||
| meta | No | ||
| error | No | ||
| needs | No | ||
| reason | No | ||
| results | No | ||
| complete | No | ||
| retryable | No | ||
| error_code | No | ||
| next_action | No | ||
| support_ref | No | ||
| invalid_fields | No | ||
| rejected_paths | No | ||
| origin_support_ref | No |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": true,
+ "properties": {
+ "code": {
+ "type": "string"
+ },
+ "complete": {
+ "type": "boolean"
+ },
+ "error": {
+ "anyOf": [
+ {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "additionalProperties": true,
+ "properties": {
+ "code": {
+ "type": "string"
+ },
+ "details": {
+ "additionalProperties": true,
+ "properties": {},
+ "type": "object"
+ },
+ "message": {
+ "type": "string"
+ },
+ "retryable": {
+ "type": "boolean"
+ },
+ "support_ref": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ }
+ ]
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "error_code": {
+ "type": "string"
+ },
+ "invalid_fields": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "meta": {
+ "additionalProperties": true,
+ "properties": {
+ "complete": {
+ "type": "boolean"
+ },
+ "has_more": {
+ "type": "boolean"
+ },
+ "limit": {
+ "type": "integer"
+ },
+ "next_continuation": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "next_cursor": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "pagination_complete": {
+ "type": "boolean"
+ },
+ "returned_count": {
+ "type": "integer"
+ },
+ "source": {
+ "type": "string"
+ },
+ "total_count": {
+ "anyOf": [
+ {
+ "type": "integer"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "truncated": {
+ "type": "boolean"
+ }
+ },
+ "type": "object"
+ },
+ "needs": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "next_action": {
+ "anyOf": [
+ {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "additionalProperties": true,
+ "properties": {},
+ "type": "object"
+ }
+ ]
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "ok": {
+ "type": "boolean"
+ },
+ "origin_support_ref": {
+ "type": "string"
+ },
+ "reason": {
+ "type": "string"
+ },
+ "rejected_paths": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "results": {
+ "items": {
+ "additionalProperties": true,
+ "properties": {},
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "retryable": {
+ "type": "boolean"
+ },
+ "support_ref": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+}Input schema / properties / connection_contextAdded value: +{
+ "pattern": "^mctx_v1_[0-9a-f]{64}$",
+ "type": "string"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact — that visible rows are partial and totals come from server-side summaries — but leaves 'ledger-backed' undefined and says nothing about caching/consistency semantics or per-scope error behavior.
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?
Two short, front-loaded sentences with no filler; the scope limit appears first. It is efficient, though the second sentence reads as an aside rather than a structured usage rule.
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?
This is a batch tool taking up to 20 nested scope objects with 17 undocumented fields each. With no parameter documentation and no explanation of batching, pagination interaction, or per-scope failure handling, the description is too thin for the complexity, even though an output schema exists.
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% for all practical purposes: only customer_id is documented, while page, page_size, view_mode, consistency, require_complete_range, sort_key, group_by and the rest carry no descriptions. The description adds no meaning for any of these, so the nested scopes contract is opaque.
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?
It names the resource (insights overview) and a concrete scope limit (up to 20 scopes), which hints that this is the batch counterpart of google_ads_insights_overview_query. However, 'Ledger-backed' is unexplained jargon and the sibling single-scope tool is never named, so the agent must infer the distinction from the tool name 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?
"Use server summaries instead of summing visible rows" is an aggregation caution, not tool-selection guidance. Nothing says when to call this versus google_ads_insights_overview_query or google_ads_insights_query_daily, nor what prerequisites (connection_context, synced accounts) apply.
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.