Kochava for Advertisers — Official MCP Server
Server Details
No account needed — connect, sign up, and query mobile attribution data from any AI tool
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- Kochava/kochava-k4a-mcp-server
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.7/5 across 2 of 2 tools scored.
The two tools have completely distinct purposes with no overlap. One tool retrieves the Terms of Service document, while the other creates an account and gets an authentication key. The descriptions clearly differentiate their functions and the workflow dependency between them is explicitly documented.
Both tools follow an identical naming pattern: 'kochava_free_app_analytics_' prefix followed by a descriptive verb_noun combination. The naming is perfectly consistent in structure, length, and style throughout the tool set.
With only 2 tools, this server feels significantly under-scoped for what appears to be a Kochava advertising platform integration. The tools cover only account creation and TOS retrieval, leaving out what would presumably be core functionality like analytics queries, campaign management, or reporting features that advertisers would need.
The tool surface is severely incomplete for an advertiser-facing platform. While it handles account setup, it lacks any tools for actual advertising operations like creating campaigns, managing budgets, retrieving analytics data, or monitoring performance. The server name suggests broader functionality that isn't reflected in the available tools.
Available Tools
2 toolskochava_free_app_analytics_create_acc_and_get_auth_keyAInspect
Create a new Kochava FAA (Free App Analytics) account.
IMPORTANT: The user MUST explicitly agree to the FAA Terms of Service before account creation. If tos_agreed is False, this tool will return the TOS link and stop — do NOT submit the form. Call kochava_free_app_analytics_get_tos() to retrieve and present the TOS to the user first, then call this tool again with tos_agreed=True once the user confirms agreement.
DISPLAY INSTRUCTIONS: When this tool returns a successful response, you MUST display the 'next_steps' field content to the user EXACTLY as written — word-for-word, preserving ALL text, formatting, line breaks, numbering, and bullet points. Do NOT summarize, rephrase, reword, or omit any part of the 'next_steps' content. Every sentence must be shown to the user as-is.
FAA Terms of Service: https://s34035.pcdn.co/wp-content/uploads/2023/08/FAA-Web-Sign-Up-TOS-8-15-23.pdf
Example (after user reviews and agrees to TOS): kochava_free_app_analytics_create_acc_and_get_auth_key( first_name="Jane", last_name="Smith", email_address="jane@example.com", phone_number="5551234567", company="Acme Corp", website="www.acme.com", company_address_line_1="123 Main St", company_city="Sandpoint", company_region="Idaho", company_postal_code="83864", country="United States", tos_agreed=True )
| Name | Required | Description | Default |
|---|---|---|---|
| title | No | Job title of the account holder (optional) | |
| company | Yes | Company name for the FAA account | |
| country | Yes | Country name (e.g. United States) | |
| privacy | No | Privacy policy URL. Defaults to https://www.kochava.com/company/contact/ | https://www.kochava.com/company/contact/ |
| website | Yes | Company website URL (e.g. www.example.com) | |
| last_name | Yes | Last name of the account holder | |
| subscribe | No | Whether to subscribe to Kochava marketing communications | |
| first_name | Yes | First name of the account holder | |
| tos_agreed | No | Whether the user has agreed to the FAA Terms of Service at https://s34035.pcdn.co/wp-content/uploads/2023/08/FAA-Web-Sign-Up-TOS-8-15-23.pdf. Must be True to proceed with account creation. Use kochava_free_app_analytics_get_tos() to share the TOS link with the user before calling this tool. | |
| company_city | Yes | Company city | |
| phone_number | Yes | Phone number of the account holder | |
| email_address | Yes | Email address for the FAA account | |
| company_region | Yes | Company state or region | |
| company_postal_code | Yes | Company postal/zip code | |
| company_address_line_1 | Yes | Company street address line 1 | |
| company_address_line_2 | No | Company street address line 2 (optional) |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It thoroughly explains the tool's behavior: it returns the TOS link and stops if tos_agreed is False, requires explicit user agreement, and mandates exact display of the 'next_steps' field content. It also includes the TOS URL and an example, covering critical operational details beyond basic functionality.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is appropriately structured with clear sections (purpose, important instructions, display instructions, TOS link, example). However, it is lengthy due to detailed procedural guidance and an extensive example. While all content is valuable, it could be more concise by reducing redundancy in instructions.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity (account creation with legal agreement), no annotations, and an output schema (implied by reference to 'next_steps' field), the description is highly complete. It covers purpose, usage prerequisites, behavioral constraints, display requirements, TOS details, and a full example, leaving no gaps for the agent to operate correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents all parameters. The description adds value by emphasizing the critical role of tos_agreed (must be True to proceed) and providing a comprehensive example that illustrates proper usage with all required parameters. However, it does not add significant semantic context beyond what the schema provides for other parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the specific action ('Create a new Kochava FAA account') and distinguishes it from the sibling tool (kochava_free_app_analytics_get_tos). It explicitly mentions the verb 'create' and the resource 'account', making the purpose unambiguous and distinct from alternatives.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides explicit guidance on when to use this tool vs. alternatives: it instructs to call kochava_free_app_analytics_get_tos first to retrieve the TOS, present it to the user, and only call this tool with tos_agreed=True after user confirmation. It also specifies prerequisites (user agreement) and exclusions (do not submit if tos_agreed is False).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
kochava_free_app_analytics_get_tosAInspect
Retrieve the FAA (Free App Analytics) Terms of Service document link.
Use this tool when the user wants to review the Terms of Service before creating an FAA account. Returns a clickable link to the TOS document and instructions for account creation.
Example: kochava_free_app_analytics_get_tos()
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden and does well by disclosing key behaviors: it returns a clickable link and account creation instructions. However, it doesn't mention potential rate limits, authentication requirements, or error conditions that might be relevant for a production API.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Perfectly structured with purpose statement, usage guidance, and example in three clear sentences. Every sentence adds value with zero redundancy. The information is front-loaded with the most important details first.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (0 parameters, has output schema), the description provides complete context: purpose, when to use, what it returns, and an example. The output schema will handle return value details, so the description appropriately focuses on usage context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has 0 parameters with 100% schema coverage, so the baseline is 4. The description appropriately doesn't discuss parameters since none exist, maintaining focus on the tool's purpose and output.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the specific action ('Retrieve') and resource ('FAA Terms of Service document link'), distinguishing it from the sibling tool which creates accounts. It goes beyond the tool name by specifying it's for Free App Analytics and what exactly is retrieved.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly states when to use this tool ('when the user wants to review the Terms of Service before creating an FAA account'), providing clear context and distinguishing it from the sibling account creation tool. The guidance is specific and actionable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!