Skip to main content
Glama

Ad-o-matic Free Mobile App Cross-Promotion

adomatic_get_integration

Read-onlyIdempotent

Generate the 1-line HouseAdBanner integration snippet and SDK download URLs (or full single-file SDK source code) for Android Jetpack Compose, iOS SwiftUI, Flutter, React Native, or Hybrid WebView. Read-only; does not register the app or modify server state. Returns platform, packageName, oneLineSnippet, targetAudienceGuidance, zeroDependencySdkUrl, mirrorSdkUrl, selfPreviewTestPeriodDays, stepsForAiAgent, and (when includeFullSdkSource is true and platform is not web) sdkSourceCode. Usage: call first when adding Ad-o-matic to an app codebase; call adomatic_onboard_app afterward to register the app, or adomatic_verify_integration to inspect an existing registration.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "adomatic_get_integration"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformNoTarget mobile framework SDK. Defaults to "android" when omitted.android
bannerTextNoShort benefit-driven banner tagline compiled into the app build (max 90 chars). Omit to generate a minimal snippet without inline copy.
packageNameNoReverse-DNS Android applicationId or iOS bundleId embedded into the generated snippet. Defaults to "com.company.myapp" for preview when omitted.com.company.myapp
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.
includeFullSdkSourceNoWhen true, embeds the complete single-file SDK source code in sdkSourceCode (Android, iOS, Flutter, React Native only; omitted for web). Defaults to false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / bannerText / description
      Previous value: -"Optional short benefit-driven ad text compiled into the app build (max 90 chars)"New value: +"Short benefit-driven banner tagline compiled into the app build (max 90 chars). Omit to generate a minimal snippet without inline copy."
    • addedInput schema / properties / bannerText / examples
      Added value: +[
      +  "Offline guitar chord tuner & metronome"
      +]
    • addedInput schema / properties / bannerText / maxLength
      Added value: +90
    • addedInput schema / properties / includeFullSdkSource / default
      Added value: +false
    • changedInput schema / properties / includeFullSdkSource / description
      Previous value: -"Set true to return the full zero-dependency single-file SDK source code ready to write into the project"New value: +"When true, embeds the complete single-file SDK source code in sdkSourceCode (Android, iOS, Flutter, React Native only; omitted for web). Defaults to false."
    • addedInput schema / properties / packageName / default
      Added value: +"com.company.myapp"
    • changedInput schema / properties / packageName / description
      Previous value: -"App packageName or bundleId (e.g. com.acme.myapp)"New value: +"Reverse-DNS Android applicationId or iOS bundleId embedded into the generated snippet. Defaults to \"com.company.myapp\" for preview when omitted."
    • 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_-]+)+$"
    • addedInput schema / properties / platform / default
      Added value: +"android"
    • changedInput schema / properties / platform / description
      Previous value: -"Target app framework/platform SDK (android, ios, flutter, react-native, or web)"New value: +"Target mobile framework SDK. Defaults to \"android\" when omitted."
    • 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"
      +]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, but the description adds the meaningful boundary that it 'does not register the app or modify server state', which clarifies the split from onboard_app. With no output schema present, the enumerated return keys (platform, oneLineSnippet, zeroDependencySdkUrl, mirrorSdkUrl, selfPreviewTestPeriodDays, stepsForAiAgent) plus the conditional sdkSourceCode rule add real value. The restated 'Read-only' is mildly redundant with the annotations, keeping this short of 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?

Front-loaded with the core action, then behavior, then the return payload, then routing guidance — a logical order with no filler sentences. The long comma-separated return-field list is justified given there is no output schema, though the platform enumeration and 'Read-only' restate structured data and could be trimmed.

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 zero-required-parameter, read-only generation tool, the description covers purpose, safety scope, full return payload including conditional fields, and sibling routing. Annotations plus 100% schema coverage plus the explicit output-field inventory leave nothing an agent needs missing before invoking it.

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 every parameter already carries its own description, default, enum, and pattern. The description's main parameter-relevant contribution is the conditional 'includeFullSdkSource is true and platform is not web', but the schema already states the same web exclusion. Baseline 3 is appropriate since the schema is doing the heavy lifting.

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?

States a specific verb plus a concrete artifact: 'Generate the 1-line HouseAdBanner integration snippet and SDK download URLs (or full single-file SDK source code)', and enumerates the five supported platforms. It explicitly distinguishes itself from siblings by naming onboard_app (registration) and verify_integration (inspecting existing registrations).

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?

Gives explicit sequencing and alternatives: 'call first when adding Ad-o-matic to an app codebase', then 'adomatic_onboard_app afterward to register the app', or 'adomatic_verify_integration to inspect an existing registration'. The when/when-not decision is fully resolved without needing to open any sibling schema.

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.