Skip to main content
Glama
Sign In
Google Ads MCP Server

Google Ads MCP Server

by adkit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get setup guide

get_setup_guide
Read-onlyIdempotent

Get step-by-step instructions to connect an AI app to the hosted Google Ads MCP server, including the exact menu path, command, or config snippet needed for setup.

Instructions

Get the step-by-step instructions to connect one AI app to the hosted Google Ads MCP server by AdKit at https://mcp.adkit.so/google-ads. Use this when the user asks how to install, add or connect AdKit in a specific app. Returns Markdown with the exact menu path, command or config snippet. For what the hosted server can do once connected, use list_hosted_tools instead.

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": {
      "app": "<app>"
    },
    "name": "get_setup_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYesThe AI app to connect, exactly as listed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value beyond them by disclosing the return payload ('Markdown with the exact menu path, command or config snippet'), which matters since there is no output schema. It stops short of noting anything about freshness or offline behavior, so it is not exhaustive.

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

Conciseness5/5

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

Three short sentences, front-loaded with the purpose, then the trigger, then the return shape and the routing alternative. No redundant or filler wording.

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

Completeness5/5

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

For a single-parameter, read-only lookup tool with full schema coverage, the description supplies purpose, trigger, output format, and sibling routing. Nothing needed to call it correctly is missing, and the absence of an output schema is compensated by the stated Markdown return content.

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

Parameters3/5

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

Schema description coverage is 100% and the single parameter is an enum with a 'exactly as listed' description, so the schema already does the work. The description only echoes that the target is 'one AI app' and 'a specific app', adding no format or selection guidance beyond the enum.

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

Purpose5/5

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

States a specific verb and resource: 'Get the step-by-step instructions to connect one AI app to the hosted Google Ads MCP server by AdKit', including the endpoint URL and a pointer to the sibling it is not (list_hosted_tools). An agent can distinguish it from list_hosted_tools and get_faq without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit trigger condition ('when the user asks how to install, add or connect AdKit in a specific app') and an explicit exclusion plus alternative ('For what the hosted server can do once connected, use list_hosted_tools instead'). Both when-to-use and when-not-to-use are covered.

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