Adwords MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_completionD | – |
| analyze_codeD | – |
| developer_tipD | – |
| gcD | – |
| acD | – |
| tipD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
The tools have no descriptions, making it impossible to determine their purposes or distinguish between them. Tools like 'ac' and 'gc' are cryptic abbreviations, while 'tip' and 'developer_tip' appear redundant, suggesting high ambiguity and overlap in functionality.
Naming is inconsistent with a mix of styles: abbreviations ('ac', 'gc'), snake_case ('analyze_code', 'get_completion'), and plain terms ('developer_tip', 'tip'). There is no clear pattern, making it difficult to predict tool functions from their names alone.
With 6 tools, the count is reasonable for a typical server scope, but the lack of descriptions makes it hard to assess if this number is appropriate. It neither feels excessively large nor too small, but the ambiguity reduces its effectiveness.
Without descriptions, it is impossible to infer the domain or assess coverage. The server name 'Adwords MCP' suggests a Google Ads domain, but the tools do not clearly relate to ad management, indicating severe incompleteness and potential gaps in functionality.