Skip to main content
Glama
Sign In
Google Ads MCP Server

Google Ads MCP Server

by anegash
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_call_extensions

Add call extensions to Google Ads accounts by providing customer ID and phone numbers with country codes.

Instructions

Create call extensions

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "customerId": "<customerId>",
      "callExtensions": "<callExtensions>"
    },
    "name": "create_call_extensions"
  }
}

Input Schema

NameRequiredDescriptionDefault
customerIdYesGoogle Ads customer ID
callExtensionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'create' but does not explain idempotency, duplicate handling, whether it replaces existing extensions, or any side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is under-specified rather than concise. It is a single phrase with no useful content, which is not the same as being appropriately minimal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a mutation tool with no annotations, no output schema, and minimal parameter documentation. The description fails to provide any context about return values, errors, permissions, or behavioral implications.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds no meaning to the input schema. The schema itself only describes half the parameters (customerId), and the description does not clarify what 'callExtensions' contains or how the fields are used.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Create call extensions' is a direct restatement of the tool name, providing no additional specificity. It does not distinguish this tool from sibling tools like create_sitelink_extensions or create_callout_extensions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given on when to use this tool versus alternatives. There is no mention of prerequisites, scenarios, or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools