Skip to main content
Glama

google_ads_conversions_get

Retrieve detailed configuration for a specific Google Ads conversion action by its numeric ID. Returns the action's ID, name, type, status, and category.

Instructions

Fetch one conversion action's configuration from Google Ads by numeric ID. Returns {id, name, type (ConversionActionType enum string, e.g. 'WEBPAGE'), status ('ENABLED'|'HIDDEN'|'REMOVED'|'UNSPECIFIED'|'UNKNOWN'), category (enum string, e.g. 'PURCHASE', 'SIGNUP')} or null when no row matches. Read-only; does NOT return value settings or lookback-window values — use the Google Ads UI for those. For the HTML/JS tag snippet to embed on a site use google_ads_conversions_tag; for full listings use google_ads_conversions_list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customer_idNoGoogle Ads customer ID as a 10-digit string without dashes (e.g. '1234567890'). Optional — falls back to GOOGLE_ADS_CUSTOMER_ID / GOOGLE_ADS_LOGIN_CUSTOMER_ID from the configured credentials when omitted.
conversion_action_idYesConversion action ID as a numeric string (e.g. '987654321'). Obtain via google_ads_conversions_list.
Behavior5/5

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

Discloses return shape, null for missing, and explicitly states what is NOT returned (value settings, lookback) — fully transparent without annotations.

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

Conciseness4/5

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

Multiple sentences but each adds value; slightly longer than minimal but not wasteful.

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?

No output schema, but description fully explains return structure and limitations; complete for a simple get tool.

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?

Schema covers both params completely; description adds fallback behavior for customer_id and source for conversion_action_id, providing useful context beyond schema.

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?

Clearly states action 'Fetch one conversion action's configuration by numeric ID', specifies resource, and distinguishes from sibling tools like list and tag.

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?

Explicitly notes read-only nature, directs to UI for missing fields, and contrasts with related tools for tag snippet or full listings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/logly/mureo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server