Skip to main content
Glama
Adjust MCP server

Adjust MCP server

by get-mcp-ads

adjust run report

adjust_run_report
Read-onlyIdempotent

Run an Adjust attribution and performance report for an allowlisted app over a date range, returning native totals, metrics, dimensions, and filters without altering values.

Instructions

Read an attribution/performance report for one allowlisted Adjust app. Preserves native totals, warnings, attribution options, currency and UTC offset. Missing metrics are null; ratios are native fractions. A truncated or partial result is not a complete extraction.

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": {
      "appToken": "<appToken>",
      "startDate": "<startDate>",
      "endDate": "<endDate>"
    },
    "name": "adjust_run_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDisplay row limit only; truncation is explicit and native totals are preserved.
endDateYesLast date of the reporting period, in YYYY-MM-DD format, on or after startDate.
filtersNoFilters combined according to this tool's query schema. Use provider field names and the declared operators.
metricsNoNative or documented calculated metric names to request. Check compatibility with the selected dimensions.
osNamesNoOperating system filter, for example ios or android. Keep os_name in dimensions to compare platforms.
appTokenYesExact Adjust application token from ADJUST_APP_TOKENS. Applications are separate from advertising accounts.
currencyNoExplicit ISO currency for money metrics. Keep the same currency across comparisons.
startDateYesFirst date of the reporting period, in YYYY-MM-DD format.
utcOffsetNoFixed UTC offset; +00:00 by default. Split local-date comparisons if the offset changes during the period.+00:00
dimensionsNoNative reporting dimensions. Validate compatibility with the selected metrics.
adSpendModeNoNative source of ad spend. Keep the same mode across comparisons and avoid counting overlapping spend twice.network
reattributedNoInclude all users, reattributed users only, or users without reattribution.all
cohortMaturityNoInclude current cohort values or use mature-only mode, which may zero immature cohorts.immature
iapRevenueModeNoIn-app revenue percentage. Retain the same setting across comparisons.GROSS_100
attributionTypesNoOptional engagement filter. Omit for an unfiltered report including native organic data. Empty types in output means no engagement filter.
attributionSourceNoAssign activity to the first install source or the native dynamic reattribution source.dynamic

Output Schema

NameRequiredDescriptionDefault
resultYesOriginal tool result: parsed JSON when the text is JSON, otherwise the text or multiple MCP content blocks. Provider fields depend on the selected query.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.1
    • changedOutput schema / properties / result / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "properties": {},
      -    "type": "object"
      -  },
      -  {
      -    "items": {},
      -    "type": "array"
      -  },
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {},
      +    "properties": {},
      +    "type": "object"
      +  },
      +  {
      +    "items": {},
      +    "type": "array"
      +  },
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. First observedv1.0.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare this as a safe, read-only, idempotent, non-destructive operation. The description adds useful behavioral context beyond annotations, including preservation of native totals/warnings/options and the warning that truncated or partial results are not complete extractions.

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?

The description is short, front-loaded with the core purpose, and each sentence contributes useful semantics. The final truncation warning is slightly redundant in wording but still earns its place as a usage caveat.

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

Completeness3/5

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

A full input schema, annotations, and an output schema carry most of the operational detail, so the description does not need to explain return values or parameters. However, for a complex report tool with a compare-periods sibling, it should do more to explain when this tool is preferable to alternatives.

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%, so the schema already documents all 16 parameters in detail. The description adds only high-level semantics such as preserved currency and UTC offset, so the baseline 3 is appropriate.

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?

The description states a specific verb and resource: reading an attribution/performance report for one allowlisted Adjust app. It is clear enough to distinguish from list/catalog sibling tools, but it does not explicitly contrast with adjust_compare_periods.

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 provides no explicit when-to-use guidance, no exclusions, and no named alternatives. An agent must infer selection from the tool name and purpose alone.

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