Export stored Console metrics as CSV
| Name | Required | Description | Default |
|---|---|---|---|
| scope | Yes | ||
| search | No | ||
| date_to | Yes | ||
| group_by | Yes | ||
| date_from | Yes | ||
| attribution | No | ||
| export_mode | No | grouped | |
| status_filter | No | ||
| confirm_export | No | ||
| connection_context | No |
| Name | Required | Description | Default |
|---|---|---|---|
| message | No | ||
| retryable | No | ||
| support_ref | No |
Changes observed during successful MCP inspections.
Output schema / else / then / properties / categoryAdded value: +{
+ "type": "string"
+}Output schema / else / then / properties / expectedAdded value: +{
+ "type": "boolean"
+}Output schema / else / then / properties / failure_kindAdded value: +{
+ "type": "string"
+}Output schema / else / then / properties / responsibility_hintAdded value: +{
+ "type": "string"
+}Output schema / else / then / properties / routeAdded value: +{
+ "type": "string"
+}Output schema / else / then / properties / user_visibleAdded value: +{
+ "type": "boolean"
+}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 declare readOnlyHint=false with destructiveHint=false, implying a non-destructive write (likely creating an export artifact), but the description never reconciles 'Export ... as CSV' with that. It omits the confirm_export confirmation step, whether a file is created or returned inline, and any rate/quota behavior — all things annotations do not cover.
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?
A single front-loaded sentence with no filler, which is structurally clean. However, at seven words it is undersized for a 10-parameter tool with four required fields and a confirmation flag, so conciseness is achieved at the cost of adequacy.
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 need not be explained, but the description leaves everything else uncovered: required scope shape, date/attribution/grouping semantics, and the confirm_export two-step behavior. For a tool this complex, the definition is materially incomplete.
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 10 parameters, including a required discriminated 'scope' object and required group_by/date_from/date_to. The description mentions none of them, so an agent gets zero guidance on defaults, the date format, grouping granularity, or the confirm_export flag.
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 specific verb+resource+format: export stored Console metrics as CSV. Clear enough that an agent knows what it produces, but it does no sibling differentiation against the very similarly named insights_export_csv or console_query_overview, which an agent would plausibly confuse it with.
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?
No indication of when to use this over insights_export_csv (also a CSV export) or console_query_overview, and no prerequisites such as connection setup or confirm_export flow. Usage context is left entirely to inference from the name.
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.