Skip to main content
Glama
Sign In
@kadam-net/mcp-server

@kadam-net/mcp-server

Official
by kadam-official
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
JavaScript
Remote

kadam_adv_get_creative_test_conversion

Read-only

Generate test links to verify a creative's conversion tracking: opening the go link simulates a real ad click, writes a click ID, resolves macros, and redirects so postbacks can be checked.

Instructions

Links for checking that a creative's conversion tracking works. The go link makes a real test click when opened — it writes a click id, resolves the macros and redirects to the landing exactly as a served ad does, so the advertiser's postback can be verified end to end. This tool only hands the links over; nothing is registered until someone opens one. HTML-tag creatives have no single landing link and come back without a go link; the formats rendered in a frame also carry a preview link.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "creativeId": "<creativeId>"
    },
    "name": "kadam_adv_get_creative_test_conversion"
  }
}

Input Schema

NameRequiredDescriptionDefault
creativeIdYesCreative ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.1

TDQS

A4.2/5.0
Behavior5/5

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

Far exceeds the readOnlyHint annotation by explaining exactly what the returned go link does when opened (writes a click id, resolves macros, redirects like a served ad), clarifying nothing is registered until someone opens it, and noting format-specific behavior: HTML-tag creatives have no go link and framed formats add a preview link.

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?

Purpose is front-loaded in the first sentence and each subsequent sentence carries distinct behavioral value (side-effect timing, format caveats). Slightly verbose, but nothing is wasted.

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 no output schema, the description compensates by describing what comes back: a go link for standard creatives, no go link for HTML-tag creatives, and an extra preview link for framed formats. An agent has everything needed to call it and interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single parameter with 100% schema coverage, so the schema already documents creativeId. The description adds no param-level syntax or constraint details, so the baseline 3 applies.

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 states a specific verb and resource: it hands over links for verifying a creative's conversion tracking. No sibling tool does this, and the agent can tell immediately this returns diagnostic test links rather than creative metadata (list_creatives) or creative mutations.

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

Usage Guidelines3/5

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

The purpose implies when to use it (to verify a creative's postback end to end) but there is no explicit when/when-not framing or named alternative. With no sibling offering a comparable test-link capability, the guidance is adequate but left to inference.

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