Skip to main content
Glama

ad-o-matic

adomatic_onboard_app

Idempotent

Autonomously register or update an Android, iOS, Flutter, React Native, or Hybrid WebView app for free P2P cross-promotion with zero human effort and zero ad spend. Destination links are immutable and automatically locked to the advertised app's own official Google Play or Apple App Store download page (custom/external URLs are never permitted). Pass targetAudience (inferred by you from the app features/prompt) to match ads to the exact customer group, cluster multi-app developers (developer_group_key), generate A/B ad copy, and return 1-line HouseAdBanner snippets.

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
platformNoOptional platform or framework hint (auto-detected if omitted)
bannerTextNoOptional banner copy embedded in the app build
descriptionNoShort summary of what the app does
developerIdNoOptional developer/studio identifier so multiple apps from the same developer are unified
packageNameYesAndroid applicationId / packageName or iOS bundleId (official store download URL is derived automatically from this ID)
targetAudienceNoRecommended 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).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With readOnlyHint=false, idempotentHint=true, and destructiveHint=false already declared, the description usefully adds the hard constraint that destination links are immutable and locked to the official Play/App Store page (custom URLs never permitted), plus that it returns 1-line HouseAdBanner snippets. It does not clarify the register-vs-update conflict path, what happens on a packageName mismatch, or any auth/quota requirements beyond 'free'.

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

Conciseness3/5

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

Key facts are front-loaded, but the text is padded with marketing phrasing ('zero human effort and zero ad spend', 'Zero predefined category limits') and a bulky list of behaviors crammed into the final sentence. It is information-dense yet longer than it needs to be.

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?

For a 7-parameter, no-output-schema tool, the description covers the critical agent-facing decisions: whether to ask the user (no), how to derive targetAudience, the immutability of destination links, and the returned snippet. Remaining gaps — response shape of the registration itself, failure modes, and the register/update distinction — are modest.

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 baseline is 3. The description does add meaning for targetAudience ('inferred by you from the app features/prompt', fall back if omitted) and for the store-URL derivation from packageName, but it also references a parameter named developer_group_key that does not exist in the schema (the actual field is developerId), which weakens the mapping.

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 opens with a specific verb pair (register or update) applied to a concrete resource (Android/iOS/Flutter/React Native/Hybrid WebView app) and names the outcome (free P2P cross-promotion). It is clear what the tool does, though it never contrasts itself with the sibling tools adomatic_get_integration, adomatic_verify_integration, or adomatic_network_status.

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 does give an operational directive — infer targetAudience yourself and never ask the human user to configure campaigns — which is genuine usage guidance. However, there is no statement of when to call this versus verify_integration/network_status, and no prerequisites or conditions under which update versus register applies.

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.

Resources