Delete AdsAgent-owned product-card metadata.
| Name | Required | Description | Default |
|---|---|---|---|
| card_id | Yes | ||
| connection_context | No |
| Name | Required | Description | Default |
|---|---|---|---|
| ok | No | ||
| code | No | ||
| error | No | ||
| needs | No | ||
| reason | No | ||
| product | 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"
+ },
+ "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"
+ },
+ "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"
+ },
+ "product": {
+ "additionalProperties": true,
+ "properties": {},
+ "type": "object"
+ },
+ "reason": {
+ "type": "string"
+ },
+ "rejected_paths": {
+ "items": {
+ "type": "string"
+ },
+ "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 destructiveHint=true and readOnlyHint=false, so the core safety profile is covered. The description adds the meaningful constraint that only AdsAgent-owned metadata is affected, but it does not explain irreversibility, permission requirements, or behavior for non-owned cards.
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 single sentence is front-loaded and free of waste, clearly stating the action and scope. It is perhaps too terse, but that is more a completeness issue than a conciseness problem.
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?
Annotations cover the destructive safety profile and an output schema exists, but the description omits essential parameter context for a destructive tool. With no schema descriptions and no mention of card_id, the definition is not complete enough for reliable invocation.
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%, and the description does not mention either parameter. The required card_id and optional connection_context are completely undocumented, leaving the agent to rely solely on parameter names.
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 description states a specific verb and resource: delete product-card metadata, scoped to AdsAgent-owned items. It distinguishes deletion from the sibling save/update/list product-card tools, though it does not explicitly name an alternative.
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 versus google_ads_product_card_update or google_ads_product_card_save, nor any prerequisites or warnings about the destructive nature. The agent must infer usage entirely from the tool 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.