Skip to main content
Glama
Adjust MCP server

Adjust MCP server

by get-mcp-ads

adjust compare periods

adjust_compare_periods
Read-onlyIdempotent

Compares two equal-length periods for an Adjust app using identical metrics and filters, defaulting to the immediately preceding period to reveal changes.

Instructions

Compare two equal-length periods for one allowlisted Adjust application with identical metrics, filters, OS and measurement settings. Defaults to the immediately preceding period. Changes use native totals, never sums of breakdowns. Unavailable or partial values have no calculated change; cohort maturity and reporting delays still apply.

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_compare_periods"
  }
}

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
comparisonNoOptional equal-length comparison period; otherwise use the immediately preceding period.
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

A5/5.0
Behavior5/5

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

The description adds vital operational context beyond the annotations and schema. It specifies that 'Changes use native totals, never sums of breakdowns' and details limitations regarding partial values and cohort maturity, which are critical behavioral constraints for an AI agent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is highly concise. It uses two sentences to articulate the complex requirements, technical constraints (native totals), default behaviors, and limitations without any superfluous language.

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?

For a complex, constraint-heavy comparison tool, the description is complete. It covers the required data consistency (metrics, filters, OS), technical calculation methods, and operational limitations, providing everything needed for safe and correct invocation.

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

Parameters5/5

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

Given the 100% schema coverage, the description focuses on the semantic *constraints* of the parameters (e.g., all settings must be identical) and the operational logic of the tool (e.g., comparison defaults), which is highly valuable to a developer/agent.

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 tool's purpose is clear: to compare two time periods. It specifically frames the comparison around 'equal-length' periods and requires an 'allowlisted Adjust application,' making it distinct from general reporting tools like adjust_run_report.

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

Usage Guidelines5/5

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

It provides extremely explicit usage guidance by requiring that the comparison use 'identical metrics, filters, OS and measurement settings.' It also clearly defines the default behavior (immediately preceding period), guiding the user when to omit the `comparison` field.

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