A
license-
qualityD
maintenanceEnables AI assistants to answer growth questions in plain English by connecting to marketing and product data via 49 MCP tools.
Last updated
25
MIT
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.
MCP client
Glama
MCP server
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.
100% free. Your data is private.
Tool Definition Quality
A4/5.0
Tool DescriptionsA
Average 4.4/5 across 2 of 2 tools scored.
Server CoherenceB
Disambiguation5/5
The two tools have clearly distinct purposes: one retrieves the Terms of Service, the other creates an account. No overlap or ambiguity.
Naming Consistency4/5
Both tools share the 'kochava_free_app_analytics_' prefix and follow verb_noun pattern, though one uses 'create_acc_and_get_auth_key' and the other 'get_tos'. Mostly consistent with minor variation in verb complexity.
Tool Count2/5
With only 2 tools, the server feels very thin for a typical MCP server. It covers only account creation and TOS retrieval, lacking other expected functionalities.
Completeness2/5
The tool surface covers only account creation and TOS viewing. Missing tools for managing accounts, viewing analytics, or performing other common advertiser tasks, leaving significant gaps.
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 )
ParametersJSON Schema
| 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
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
Tool Definition Quality
A4.2/5.0
Behavior4/5
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 transparency. It explains that the tool requires tos_agreed=True to proceed, and if tos_agreed=False it returns the TOS link and aborts. It also includes display instructions for the output. However, the tool name suggests it returns an auth key, but the description does not mention that the output includes an authentication key or what exactly happens after account creation, which is a minor gap.
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?
The description is fairly long but well-structured with clear sections: purpose, important note, display instructions, link, and example. It front-loads the critical TOS agreement condition. Some redundancy exists (TOS link appears twice), and the display instructions could be more concise, but the organization helps readability.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is complex (16 parameters, 11 required) with no annotations. The description covers the essential TOS precondition and example usage, and it notes that output includes a 'next_steps' field. However, it fails to mention that the tool returns an auth key (as named) or any post-account-creation flow. While an output schema exists (not shown), the description should still provide context about the key result. This omission makes it slightly incomplete.
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?
The input schema already covers 100% of parameters with descriptions, so the description's parameter contribution is minimal. The description adds an example that shows realistic parameter values, but does not clarify any parameter beyond what the schema provides. Per the rubric, high schema coverage gives a baseline of 3, and the description does not significantly improve upon that.
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 clearly states the action: 'Create a new Kochava FAA (Free App Analytics) account.' It includes an example and differentiates itself from the sibling tool kochava_free_app_analytics_get_tos by describing the proper workflow. The verb 'Create' plus the resource 'account' is specific and unambiguous.
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?
The description provides explicit when-to-use and when-not-to-use guidance: it instructs the agent to first call kochava_free_app_analytics_get_tos() to present the TOS before calling this tool, and clarifies that if tos_agreed is False, the tool will stop and return the TOS link. It also includes an example to illustrate correct invocation.
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()
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
Tool Definition Quality
A4.5/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It states it returns a clickable link and instructions, implying no side effects. However, it doesn't explicitly confirm read-only behavior, but given the nature, it's sufficiently transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Concise at 2-3 sentences with an example. No fluff, front-loaded with purpose.
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?
Given zero parameters and an output schema, the description adequately explains the tool's purpose and return value. No missing context for a simple retrieval tool.
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?
No parameters, so baseline 4. Description adds no param info, but none needed. Schema coverage is 100%.
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 clearly states it retrieves the FAA Terms of Service document link, which is a specific verb+resource. It distinguishes from the sibling tool (create account) by specifying the purpose of reviewing TOS before account creation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says when to use: when user wants to review TOS before creating an FAA account. Provides context but no explicit when-not-to-use or alternatives, though the sibling tool is implied as the next step.
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!
Related MCP Servers
- Alicense-qualityFmaintenanceEnables AI to securely access and query Google Ads account data without Google Cloud setup, using GAQL.app as a backend.Last updated8550MIT
- AlicenseAqualityBmaintenanceConnects Hyros advertising attribution to AI assistants (Claude, Cursor, etc.) through the Model Context Protocol, enabling queries about leads, sales, calls, subscriptions, and ad performance.Last updated3826MIT
- AlicenseBqualityDmaintenanceConnects AI assistants like Claude to Sealmetrics analytics data, enabling natural language queries for traffic analysis, conversions, marketing performance, ROAS tracking, and funnel analysis.Last updated8MIT