get_conversion_trackerRetrieve a single conversion tracker with its postback settings by ID, so you can inspect how conversions are attributed and reported for your TrafficOX advertising account.
One conversion tracker with its postback settings.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that the response includes postback settings, which is useful context beyond the annotations, but it omits any mention of permissions, error behavior, or rate limits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single short fragment with no filler. It is front-loaded with the core scope ('one conversion tracker') and immediately appends the notable output detail ('with its postback settings').
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a get-by-id tool with no output schema and a completely undocumented required parameter, the description is too thin. It says what the object is but not how to identify it or what the return shape entails beyond postback settings.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% for the single required 'id' parameter, and the description does not mention it at all. The agent must rely solely on the schema's type and minLength constraints to know that an identifier is required.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description identifies the resource (one conversion tracker) and adds that postback settings are included. Combined with the name 'get_conversion_tracker' and the sibling 'list_conversion_trackers', an agent can distinguish this as the single-item fetch. It lacks an explicit verb, but the scope is clear.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 tool versus 'list_conversion_trackers' or other siblings. The description only states what is returned, leaving the agent to infer that this is for fetching a single record by ID.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.