Skip to main content
Glama
Adjust MCP server

Adjust MCP server

by get-mcp-ads

adjust list events

adjust_list_events
Read-onlyIdempotent

Discover native event base slugs, activity-count metric IDs, and app-specific event tokens for an allowlisted Adjust app so you can choose valid metrics for reporting.

Instructions

Discover native event base slugs, ordinary activity-count metric IDs and app-specific event tokens for one allowlisted Adjust app. Use activityMetric for counts; the event base slug alone is not a report metric. Keep SKAdNetwork and aggregate revenue definitions separate.

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>"
    },
    "name": "adjust_list_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchNoFilter native event definitions by a short search term.
appTokenYesExact Adjust application token from ADJUST_APP_TOKENS. Applications are separate from advertising accounts.

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

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds genuine domain context beyond that: the app must be allowlisted, the returned identifiers have different downstream semantics, and certain definition families must not be conflated. It omits pagination/result-cap behavior, which is why it is not a 5.

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?

Three tight sentences with the purpose front-loaded and no filler. The phrasing is jargon-dense (base slug vs activity-count metric ID vs event token) but each clause carries a distinct constraint.

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 spelled out, and the description still characterizes the three identifier kinds an agent will get back. For a two-parameter read-only lookup this is nearly sufficient; only result-size/pagination expectations are unaddressed.

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 both appToken and search are documented in the schema; a baseline of 3 applies. The description reinforces the app-token scoping ('one allowlisted Adjust app') but adds nothing about the search filter or the identifier format, so it does not exceed the schema.

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 names a specific verb ('Discover') and concrete resources ('native event base slugs, ordinary activity-count metric IDs and app-specific event tokens') scoped to 'one allowlisted Adjust app'. An agent can tell this is a discovery/enumeration tool rather than a reporting one. It does not explicitly name a sibling (e.g. adjust_get_catalog) to differentiate against, which keeps this from a 5.

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?

It gives concrete downstream guidance ('Use activityMetric for counts; the event base slug alone is not a report metric') and a segmentation warning about SKAdNetwork vs aggregate revenue, which helps the agent choose the right identifier. However, it never states when to call this versus adjust_get_catalog, adjust_list_apps, or adjust_run_report, so sibling routing is left to inference.

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