Skip to main content
Glama
shinypebble

microsoft-ads-mcp

by shinypebble

apply_offline_conversions

Import offline conversions keyed by MSCLKID, attributing each to a click and counting it under a named OfflineConversion goal.

Instructions

Import offline conversions against an OfflineConversion goal, keyed by MSCLKID.

This is the bid-eligible path for phone calls: create an OfflineConversion goal with create_conversion_goal, apply your own qualifying filter to the call-center log (e.g. keep calls >=60s), then upload one record per qualifying call. Each record is attributed to the click that drove it and counted under the goal whose name matches conversion_name. Returns per-record errors in partial_errors (the API returns no ids).

Note: wait ~2 hours after creating an OfflineConversion goal before uploading — earlier uploads are rejected with "OfflineConversionNotAcceptedForGoal" (expected, not a bug).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
conversions_to_applyYesOne or more conversions. Each has: click_id — the MSCLKID from the ad click (Microsoft auto-tags it onto landing-page URLs; see get_account_url_options); conversion_name — must match an existing OfflineConversion goal's name; conversion_time — ISO-8601 timestamp (treated as UTC if no offset given), after the click and within the goal's conversion window; value — optional conversion value (requires currency_code); currency_code — ISO 4217 code for value, e.g. "USD".

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
idsNo
messageYes
partial_errorsNo
Behavior5/5

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

Annotations indicate mutation (readOnlyHint=false), and the description expands on behavioral aspects: returns partial_errors, no ids, requires post-creation wait, and details the record attribution logic. No contradiction.

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?

Two concise paragraphs with no fluff; first sentence captures purpose, then details usage and constraints. Every sentence adds value.

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?

With 1 parameter (array), 100% schema coverage, output schema (partial_errors), and thorough description covering purpose, usage, timing, error handling, and parameter details, the tool is fully specified.

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 coverage is 100%, baseline 3. The description adds significant meaning beyond schema: explains click_id as MSCLKID, conversion_name must match goal, conversion_time as ISO-8601, and value/currency_code relationship.

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?

The description clearly states the tool imports offline conversions against an OfflineConversion goal keyed by MSCLKID, and distinguishes it from siblings by specifying its use for bid-eligible phone call conversions, referencing create_conversion_goal.

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?

Provides explicit guidance on when to use (after creating a goal, for qualifying calls) and when not to (wait ~2 hours before uploading to avoid rejection), and notes the alternative of creating a goal first.

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/shinypebble/microsoft-ads-mcp'

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