Skip to main content
Glama
Sign In
Google Ads MCP Server

Google Ads MCP Server

by adkit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get example prompts

get_example_prompts
Read-onlyIdempotent

Returns example prompts for the hosted Google Ads MCP server, covering reporting, campaign optimization, and launching. Use it to show users what to try first or ask the agent.

Instructions

Get example prompts that work with the hosted Google Ads MCP server by AdKit, such as reporting, optimizing and launching campaigns. Use this when the user asks what to try first or what to ask the agent. Returns a Markdown list.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_example_prompts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the return format ("Returns a Markdown list"), which is genuinely useful since no output schema exists, though it says nothing about how the examples are scoped or refreshed.

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 with the resource first, the trigger second, and the return type last. Nothing is redundant and nothing important is buried.

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 zero-parameter, read-only helper with no output schema, the description covers what it returns and when to reach for it. No structural gaps remain that would block a correct invocation.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. Naming the categories covered (reporting, optimizing, launching) gives a hint about what the returned prompts address.

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

Purpose4/5

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

The description names a specific verb and resource ("Get example prompts") and scopes it to the hosted Google Ads MCP server by AdKit, illustrating the topic areas (reporting, optimizing, launching campaigns). It does not explicitly separate itself from siblings like get_faq or get_setup_guide, so it stops short of full sibling differentiation.

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

Usage Guidelines4/5

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

It gives a concrete trigger: use when the user asks what to try first or what to ask the agent. That is a clear usage context, but there are no exclusions or pointers to alternatives such as get_faq for question-style requests.

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