Skip to main content
Glama
Sign In
mcp-openai-ads

mcp-openai-ads

by dienhokhanh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List conversion setup

list_conversion_setup
Read-only

Retrieve conversion pixels/sources and event settings (event type, attribution window, linked campaigns) to audit or verify ad tracking.

Instructions

List conversion pixels/sources and conversion event settings (event type, attribution window, linked campaigns).

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": "list_conversion_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful detail about what configuration fields are returned (event type, attribution window, linked campaigns), but says nothing about pagination, result size, or scoping.

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?

A single compact sentence with the resource front-loaded and the returned fields in parentheses. No filler, though it is terse enough that it leaves room for missing usage guidance.

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

Completeness4/5

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

With no parameters and no output schema, the description carries the burden of telling the agent what comes back, and it does so by naming the settings fields. It is adequate for a simple read-only listing, though a note on scope or pagination would round it out.

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; the description correctly implies a full unfiltered listing with no parameter-related gaps to fill.

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?

States a specific verb ('List') and resource ('conversion pixels/sources and conversion event settings') and enumerates the settings covered. It is distinguishable from the nearby sibling 'list_recent_conversion_events', though it does not explicitly call out the difference.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus 'list_recent_conversion_events' or the other list_* siblings. The usage context is only implied by the noun 'conversion setup'.

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