Skip to main content
Glama

DropTrack Get Ad Landing Report

droptrack_get_ad_landing_report
Read-only

Read a Grow campaign landing funnel, daily activity, country, device, source, service clicks and estimated Spotify app opens. Returns separate dated ad spend; app opens do not confirm streams.

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": {
      "campaignId": "<campaignId>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "droptrack_get_ad_landing_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesLast report date (YYYY-MM-DD), within 366 days of from
fromYesFirst report date (YYYY-MM-DD)
limitNoMaximum aggregate rows in each measurement page
campaignIdYesThe current company ads campaign ID
activityCursorNoLanding activity offset from activityNextCursor
appOutcomeCursorNoApp outcome offset from appOutcomeNextCursor

Output Schema

NameRequiredDescriptionDefault
resultNoStructured DropTrack result returned by this tool

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: figures are estimates, ad spend is returned as separate dated data, and app opens are not equivalent to streams. It says nothing about the paginated/cursor behavior that the structured schema implies.

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?

Two sentences, front-loaded with the primary action and resource, then the caveat. Dense enumeration is efficient, though the metric list reads as slightly breathless and nothing marks the funnel versus engagement metrics as distinct.

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?

An output schema exists, so return values need not be described, and the description covers what is measured plus the estimate caveat. For a six-parameter paginated report tool the remaining gap is the absence of guidance on choosing this report over the sibling analytics tools.

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?

Schema description coverage is 100%, including the date range, campaign ID, limit, and both cursor parameters, so the baseline is 3. The description adds no meaning about date-range semantics, campaign scoping, or how paging through the two cursors works beyond what the schema already states.

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?

Specific verb plus resource: "Read a Grow campaign landing funnel" followed by an enumeration of the measured dimensions (daily activity, country, device, source, service clicks, Spotify app opens). It does not explicitly distinguish itself from close siblings like droptrack_get_ad_analytics or droptrack_get_campaign_analytics, so the boundary is left to inference.

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?

The description gives no when-to-use or when-not-to-use guidance and never names an alternative report tool among the many analytics siblings. The only conditional statement ("app opens do not confirm streams") is an interpretation caveat, not a routing rule.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.