Skip to main content
Glama

Ads MCP Server by AdKit

adkit_integrations

Read-onlyIdempotent

Read connected GA4, Google Search Console, and Google Merchant Center data. See adkit_help({ path: "integrations" }) for provider actions and examples.

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": {
      "provider": "<provider>",
      "action": "<action>"
    },
    "name": "adkit_integrations"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoOptional exact page URL. GSC get_keywords only.
limitNoResult limit from 1 to 100 (default: 50). GA4 list_properties or any GSC operation.
queryNoOptional property name, account name, or property resource search. Use only with list_properties.
actionYesGA4: list_properties, get_metadata, run_report. GSC: list_sites, get_keywords, get_pages. Merchant Center: request.
deviceNoOptional GSC device filter.
offsetNoZero-based result offset (default: 0). GA4 list_properties or any GSC operation. Use nextOffset for another available page.
reportNoNative GA4 runReport request body (dateRanges, metrics, dimensions, filters, etc.). Required for run_report.
countryNoOptional GSC ISO alpha-3 country filter, e.g. USA.
endDateNoGSC inclusive end date YYYY-MM-DD (Pacific Time). Required for get_keywords/get_pages.
keywordNoOptional exact organic search query. GSC get_pages only.
requestNoRead-only Merchant API request. Required for the Merchant Center request action.
siteUrlNoGSC property from list_sites: sc-domain:example.com or https://example.com/. Required for get_keywords/get_pages.
propertyNoGA4 property resource from list_properties, e.g. "properties/123456789". Required for get_metadata and run_report.
providerYesData provider: Google Analytics 4, Google Search Console, or Google Merchant Center.
projectIdNoRequired. Get from adkit_projects. Auto-resolves only for single-project users.
startDateNoGSC inclusive start date YYYY-MM-DD (Pacific Time). Required for get_keywords/get_pages.
connectionIdNoOptional connected Google login. Use connectionId from list_properties (GA4) or list_sites (GSC) when several logins are connected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"GA4: list_properties, get_metadata, run_report. GSC: list_sites, get_keywords, get_pages."New value: +"GA4: list_properties, get_metadata, run_report. GSC: list_sites, get_keywords, get_pages. Merchant Center: request."
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "list_properties",
      -  "get_metadata",
      -  "run_report",
      -  "list_sites",
      -  "get_keywords",
      -  "get_pages"
      -]New value: +[
      +  "list_properties",
      +  "get_metadata",
      +  "run_report",
      +  "list_sites",
      +  "get_keywords",
      +  "get_pages",
      +  "request"
      +]
    • changedInput schema / properties / provider / description
      Previous value: -"Data provider: Google Analytics 4 or Google Search Console."New value: +"Data provider: Google Analytics 4, Google Search Console, or Google Merchant Center."
    • changedInput schema / properties / provider / enum
      Previous value: -[
      -  "ga4",
      -  "gsc"
      -]New value: +[
      +  "ga4",
      +  "gsc",
      +  "merchant-center"
      +]
    • addedInput schema / properties / request
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Read-only Merchant API request. Required for the Merchant Center request action.",
      +  "properties": {
      +    "connectionId": {
      +      "description": "Choose a connected Merchant Center login by ID. Required when several logins are connected.",
      +      "type": "string"
      +    },
      +    "endpoint": {
      +      "description": "Merchant API path starting with /, e.g. /accounts/v1/accounts.",
      +      "type": "string"
      +    },
      +    "method": {
      +      "description": "Use GET for reads or POST for report search.",
      +      "enum": [
      +        "GET",
      +        "POST"
      +      ],
      +      "type": "string"
      +    },
      +    "payload": {
      +      "additionalProperties": true,
      +      "description": "Native Merchant API JSON request body. Required for POST report search.",
      +      "type": "object"
      +    },
      +    "query": {
      +      "additionalProperties": true,
      +      "description": "Optional URL parameters with string, number, or boolean values.",
      +      "type": "object"
      +    }
      +  },
      +  "required": [
      +    "method",
      +    "endpoint"
      +  ],
      +  "type": "object"
      +}
  2. Changed14 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"List accessible properties, discover property-specific custom fields and key events, or run a read-only GA4 report."New value: +"GA4: list_properties, get_metadata, run_report. GSC: list_sites, get_keywords, get_pages."
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "list_properties",
      -  "get_metadata",
      -  "run_report"
      -]New value: +[
      +  "list_properties",
      +  "get_metadata",
      +  "run_report",
      +  "list_sites",
      +  "get_keywords",
      +  "get_pages"
      +]
    • changedInput schema / properties / connectionId / description
      Previous value: -"Optional connected GA4 login. Use the connectionId returned by list_properties when more than one login is connected."New value: +"Optional connected Google login. Use connectionId from list_properties (GA4) or list_sites (GSC) when several logins are connected."
    • addedInput schema / properties / country
      Added value: +{
      +  "description": "Optional GSC ISO alpha-3 country filter, e.g. USA.",
      +  "type": "string"
      +}
    • addedInput schema / properties / device
      Added value: +{
      +  "description": "Optional GSC device filter.",
      +  "enum": [
      +    "desktop",
      +    "mobile",
      +    "tablet"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / endDate
      Added value: +{
      +  "description": "GSC inclusive end date YYYY-MM-DD (Pacific Time). Required for get_keywords/get_pages.",
      +  "type": "string"
      +}
    • addedInput schema / properties / keyword
      Added value: +{
      +  "description": "Optional exact organic search query. GSC get_pages only.",
      +  "type": "string"
      +}
    • changedInput schema / properties / limit / description
      Previous value: -"Optional property result limit from 1 to 100. Use only with list_properties; defaults to 50."New value: +"Result limit from 1 to 100 (default: 50). GA4 list_properties or any GSC operation."
    • changedInput schema / properties / offset / description
      Previous value: -"Optional zero-based property result offset. Use only with list_properties; defaults to 0."New value: +"Zero-based result offset (default: 0). GA4 list_properties or any GSC operation. Use nextOffset for another available page."
    • addedInput schema / properties / page
      Added value: +{
      +  "description": "Optional exact page URL. GSC get_keywords only.",
      +  "type": "string"
      +}
    • changedInput schema / properties / provider / description
      Previous value: -"Data provider. Currently Google Analytics 4."New value: +"Data provider: Google Analytics 4 or Google Search Console."
    • changedInput schema / properties / provider / enum
      Previous value: -[
      -  "ga4"
      -]New value: +[
      +  "ga4",
      +  "gsc"
      +]
    • addedInput schema / properties / siteUrl
      Added value: +{
      +  "description": "GSC property from list_sites: sc-domain:example.com or https://example.com/. Required for get_keywords/get_pages.",
      +  "type": "string"
      +}
    • addedInput schema / properties / startDate
      Added value: +{
      +  "description": "GSC inclusive start date YYYY-MM-DD (Pacific Time). Required for get_keywords/get_pages.",
      +  "type": "string"
      +}
  3. Changed6 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"List accessible properties or run a read-only GA4 report."New value: +"List accessible properties, discover property-specific custom fields and key events, or run a read-only GA4 report."
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "list_properties",
      -  "run_report"
      -]New value: +[
      +  "list_properties",
      +  "get_metadata",
      +  "run_report"
      +]
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Optional property result limit from 1 to 100. Use only with list_properties; defaults to 50.",
      +  "type": "number"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Optional zero-based property result offset. Use only with list_properties; defaults to 0.",
      +  "type": "number"
      +}
    • changedInput schema / properties / property / description
      Previous value: -"GA4 property resource from list_properties, e.g. \"properties/123456789\". Required for run_report."New value: +"GA4 property resource from list_properties, e.g. \"properties/123456789\". Required for get_metadata and run_report."
    • addedInput schema / properties / query
      Added value: +{
      +  "description": "Optional property name, account name, or property resource search. Use only with list_properties.",
      +  "type": "string"
      +}
  4. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, and the description is consistent with a read-only integration tool. Beyond those annotations it adds little about auth requirements, rate limits, pagination behavior, or failure modes; the provider list and help pointer are useful but limited. With annotations carrying the safety profile, a 3 is appropriate.

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?

Two short sentences, front-loaded with the core purpose and followed by a targeted reference to adkit_help. No redundant wording or restatement of schema details; every sentence carries information.

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 description, annotations, and fully documented schema give enough to identify the tool and route complex provider-specific usage to adkit_help. However, for a 17-parameter, nested-request tool with no output schema, it does not describe return data, result shapes, or key operational constraints, leaving meaningful gaps. This is adequate but not complete.

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 17 parameters, enums, required conditions, and nested request object are already documented. The description adds a pointer to adkit_help for provider actions and examples, but does not itself explain action-specific parameter semantics beyond what the schema says. Baseline 3 applies.

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 uses a specific verb ('Read') and names the three resources (GA4, Google Search Console, Merchant Center), making the tool's core function clear. It does not explicitly differentiate this tool from siblings such as adkit_library or adkit_status, and only redirects to adkit_help for action details, so it falls short of full sibling differentiation.

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 implies usage for reading connected integration data and points to adkit_help for provider actions and examples. However, it gives no explicit when-to-use or when-not-to-use criteria versus sibling tools or other data-access paths, so guidance is only implied.

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.