Ads Manager by AdKit: Google Ads, Meta Ads, TikTok Ads, LinkedIn Ads

adkit_integrations

Read-onlyIdempotent

Read connected GA4 reports and Google Search Console websites, organic keywords, and pages. Provider is ga4 or gsc; the field reference is adkit_help({ path: "integrations ga4" }) or adkit_help({ path: "integrations gsc" }).

Input Schema

Name	Required	Description
`page`	No	Optional exact page URL. GSC get_keywords only.
`limit`	No	Result limit from 1 to 100 (default: 50). GA4 list_properties or any GSC operation.
`query`	No	Optional property name, account name, or property resource search. Use only with list_properties.
`action`	Yes	GA4: list_properties, get_metadata, run_report. GSC: list_sites, get_keywords, get_pages.
`device`	No	Optional GSC device filter.
`offset`	No	Zero-based result offset (default: 0). GA4 list_properties or any GSC operation. Use nextOffset for another available page.
`report`	No	Native GA4 runReport request body (dateRanges, metrics, dimensions, filters, etc.). Required for run_report.
`country`	No	Optional GSC ISO alpha-3 country filter, e.g. USA.
`endDate`	No	GSC inclusive end date YYYY-MM-DD (Pacific Time). Required for get_keywords/get_pages.
`keyword`	No	Optional exact organic search query. GSC get_pages only.
`siteUrl`	No	GSC property from list_sites: sc-domain:example.com or https://example.com/. Required for get_keywords/get_pages.
`property`	No	GA4 property resource from list_properties, e.g. "properties/123456789". Required for get_metadata and run_report.
`provider`	Yes	Data provider: Google Analytics 4 or Google Search Console.
`projectId`	No	Required. Get from adkit_projects. Auto-resolves only for single-project users.
`startDate`	No	GSC inclusive start date YYYY-MM-DD (Pacific Time). Required for get_keywords/get_pages.
`connectionId`	No	Optional 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.

Changed14 schema fields changedOct 6, 2026

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"
+}

Changed6 schema fields changedSep 29, 2026

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"
+}

AddedSep 17, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive behavior, so the safety profile is covered. The description adds that data comes from connected GA4/GSC sources and references help paths, but it does not disclose pagination, rate limits, or return behavior beyond what the schema implies.

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?

The description is two tightly written sentences with no wasted language. The core read capability is front-loaded, and the provider/help reference follows efficiently.

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?

For a 16-parameter, six-action tool with no output schema, the description is quite thin: it does not outline the available actions or describe return shape. The 100% schema coverage and help references mitigate this, but an agent still relies almost entirely on structured fields to understand the full operation set.

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 all 16 parameters are already documented in the input schema. The description only adds the provider distinction and help pointers, which is baseline-level value when the schema does the heavy lifting.

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 states a specific read operation over GA4 reports and GSC websites, organic keywords, and pages, and identifies the two providers. It does not explicitly differentiate from siblings, but no sibling appears to overlap with this data-integration purpose.

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 tells the agent that the provider is either ga4 or gsc and points to adkit_help for field references, which is useful routing guidance. However, it does not say when to use this tool versus alternatives or when not to use it, so usage is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Ads Manager by AdKit: Google Ads, Meta Ads, TikTok Ads, LinkedIn Ads tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

adkit_integrations

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources