Skip to main content
Glama

Ad-o-matic Free Mobile App Cross-Promotion

adomatic_onboard_app

Idempotent

Register or update a mobile app in the Ad-o-matic P2P cross-promotion network (idempotent upsert; repeated calls with the same packageName update metadata without duplicates). Destination store links are locked automatically to the app's official Google Play or Apple App Store page; custom URLs are never permitted. New or updated apps enter a 7-day Self-Preview Test Period before live P2P rotation. Returns locked store URL, normalized audienceSegments, suitability profile, A/B banner copy, and 1-line HouseAdBanner snippet. Rejects invalid or placeholder reverse-DNS packageName values (such as com.example.*). Usage: call after adomatic_get_integration to pre-register an app. Do not use for read-only checks — use adomatic_verify_integration for per-app status or adomatic_network_status for pool-wide metrics.

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": {
      "packageName": "<packageName>"
    },
    "name": "adomatic_onboard_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoHuman-readable app title shown in banners (max 80 chars). Inferred from packageName when omitted.
platformNoOptional OS or framework hint. Maps android and ios directly; cross-platform values or omission fall back to automatic OS inference.
bannerTextNoOptional inline banner copy compiled into the app build (max 90 chars). Auto-generated from title and description when omitted.
descriptionNoConcise summary of what the app does for audience matching (max 300 chars). Inferred automatically when omitted.
developerIdNoOptional stable developer or studio identifier used to cluster sibling apps under developer_group_key (max 100 chars). Defaults to app-level grouping when omitted.
packageNameYesReal reverse-DNS Android applicationId or iOS bundleId (5-120 chars; official Google Play or Apple App Store URL is derived automatically; placeholders like com.example.* are rejected).
targetAudienceNoFree-form natural-language customer group (2-6 personas, hobbies, or domain keywords plus optional age band 18-24, 25-44, or 45+). Omit if unknown to fall back to automatic metadata inference.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed21 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / bannerText / description
      Previous value: -"Optional banner copy embedded in the app build"New value: +"Optional inline banner copy compiled into the app build (max 90 chars). Auto-generated from title and description when omitted."
    • addedInput schema / properties / bannerText / examples
      Added value: +[
      +  "Tune faster offline — zero tracking"
      +]
    • addedInput schema / properties / bannerText / maxLength
      Added value: +90
    • changedInput schema / properties / description / description
      Previous value: -"Short summary of what the app does"New value: +"Concise summary of what the app does for audience matching (max 300 chars). Inferred automatically when omitted."
    • addedInput schema / properties / description / examples
      Added value: +[
      +  "Offline chromatic guitar tuner and chord library for acoustic and electric players."
      +]
    • addedInput schema / properties / description / maxLength
      Added value: +300
    • changedInput schema / properties / developerId / description
      Previous value: -"Optional developer/studio identifier so multiple apps from the same developer are unified"New value: +"Optional stable developer or studio identifier used to cluster sibling apps under developer_group_key (max 100 chars). Defaults to app-level grouping when omitted."
    • addedInput schema / properties / developerId / examples
      Added value: +[
      +  "acme-mobile-studio"
      +]
    • addedInput schema / properties / developerId / maxLength
      Added value: +100
    • changedInput schema / properties / packageName / description
      Previous value: -"Android applicationId / packageName or iOS bundleId (official store download URL is derived automatically from this ID)"New value: +"Real reverse-DNS Android applicationId or iOS bundleId (5-120 chars; official Google Play or Apple App Store URL is derived automatically; placeholders like com.example.* are rejected)."
    • addedInput schema / properties / packageName / examples
      Added value: +[
      +  "com.acme.invoicer",
      +  "io.studio.chordtuner"
      +]
    • addedInput schema / properties / packageName / maxLength
      Added value: +120
    • addedInput schema / properties / packageName / minLength
      Added value: +5
    • addedInput schema / properties / packageName / pattern
      Added value: +"^[a-zA-Z][a-zA-Z0-9_]*(\\.[a-zA-Z0-9_-]+)+$"
    • changedInput schema / properties / platform / description
      Previous value: -"Optional platform or framework hint (auto-detected if omitted)"New value: +"Optional OS or framework hint. Maps android and ios directly; cross-platform values or omission fall back to automatic OS inference."
    • changedInput schema / properties / targetAudience / description
      Previous value: -"Recommended when the producer AI agent knows who the app is built for (optional; falls back automatically if omitted). Pass any open-ended, free-form natural-language description of the app's customer group: 2-6 specific personas, hobbies, professions, activities, or niche keywords + optional age range (18-24 | 25-44 | 45+). Zero predefined category limits — any app domain is matched semantically across both outgoing and incoming ads (never ask the human user to configure campaigns; infer directly from the codebase/prompt)."New value: +"Free-form natural-language customer group (2-6 personas, hobbies, or domain keywords plus optional age band 18-24, 25-44, or 45+). Omit if unknown to fall back to automatic metadata inference."
    • changedInput schema / properties / targetAudience / examples
      Previous value: -[
      -  "guitarists, musicians, chord tuner, songwriting, 18-44",
      -  "amateur astronomers, stargazing, telescope owners, astrophotography",
      -  "freelancers, solo founders, small businesses, invoicing, 25-44",
      -  "knitters, crochet, yarn crafts, handmade patterns"
      -]New value: +[
      +  "guitarists, musicians, chord tuner, songwriting, 18-44",
      +  "freelancers, solo founders, invoicing, 25-44",
      +  "amateur astronomers, stargazing, telescope owners"
      +]
    • changedInput schema / properties / title / description
      Previous value: -"Human-readable app title"New value: +"Human-readable app title shown in banners (max 80 chars). Inferred from packageName when omitted."
    • addedInput schema / properties / title / examples
      Added value: +[
      +  "ChordCraft Tuner"
      +]
    • addedInput schema / properties / title / maxLength
      Added value: +80
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already establish idempotency and non-destructiveness, yet the description still adds substantial behavior: destination store links are auto-locked and custom URLs are never permitted, new/updated apps enter a 7-day Self-Preview Test Period before live rotation, and placeholder reverse-DNS values are rejected. It also enumerates what the call returns (locked store URL, normalized audienceSegments, suitability profile, banner copy, HouseAdBanner snippet), which the annotations do not cover.

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?

Front-loaded with the core action and upsert semantics, then behavior, then routing. Dense but nearly every clause carries decision-relevant information; the return-value enumeration is the only mildly over-specified portion. No filler or restatement of the name.

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 7-parameter mutation with no output schema, the description supplies the missing pieces: idempotency behavior, URL locking rules, the 7-day preview gating, validation failures, and the return payload. An agent can call this correctly and anticipate results without further documentation.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns extra by explaining that repeated calls with the same packageName update rather than duplicate, giving packageName a semantic role as the idempotency key, and by restating the rejection of placeholder values like com.example.*. Other parameters (title, bannerText, targetAudience) are left entirely to the schema, which is acceptable given its richness.

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 opens with a specific verb and resource ("Register or update a mobile app") and qualifies the scope (P2P cross-promotion network, idempotent upsert). It names the sibling tools it is *not* (adomatic_verify_integration, adomatic_network_status), so an agent can select correctly without opening the schema.

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?

Explicit ordering guidance ("call after adomatic_get_integration to pre-register an app") plus a clear negative case ("Do not use for read-only checks") that routes to two named alternatives with their specific purposes. Both when-to-use and when-not-to-use are stated.

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.