Update AdsAgent-owned product-card metadata.
| Name | Required | Description | Default |
|---|---|---|---|
| card_id | Yes | ||
| merge_keys | No | ||
| description | No | ||
| display_name | No | ||
| funnel_events | No | ||
| decision_rules | No | ||
| 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?
The annotations already declare readOnlyHint=false and destructiveHint=true. The description adds the useful 'AdsAgent-owned' ownership constraint, but does not explain what is destructive, whether updates merge or replace fields, or what happens to existing metadata.
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 bloat. However, for a 7-parameter destructive mutation, this level of terseness is not appropriately sized.
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 output schema and annotations provide some supporting context, but the description leaves critical gaps for a destructive 7-parameter update. With zero schema description coverage, an agent cannot tell what fields are updateable or how merge_keys and decision_rules behave.
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?
There are 7 parameters with 0% schema description coverage, and the description does not mention any of them. It provides no meaning for card_id, merge_keys, display_name, description, funnel_events, decision_rules, or the pattern-constrained connection_context.
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 has a clear verb and resource: 'Update ... product-card metadata.' The 'AdsAgent-owned' qualifier usefully narrows scope, but 'metadata' is vague and does not distinguish this tool from the related product_card_save operation.
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 explicit guidance on when to use this tool instead of google_ads_product_card_save, google_ads_product_card_delete, or google_ads_product_cards_list. Usage is only implied by the verb 'Update.'
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.