Install Jentic One Beta

Connect the Get MCP Ads Data API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Get MCP Ads Data API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgetmcpads.com%2Fgetmcpads" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgetmcpads.com%2Fgetmcpads" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Get MCP Ads Data API.

List the accounts and report sources the current key is allowed to read

Discover the metrics, dimensions, and levels available for a report source

Query a report where larger requests return an asynchronous extraction

Read extraction status, immutable result pages, and the full download

Schedule syncs that push report results to allowed destinations on a cadence

GET STARTED

Start building with Get MCP Ads Data API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Get MCP Ads Data API for, with concrete tasks.

★ Agent-run advertising report pull

An AI agent preparing a performance summary can call the getmcpads.com API through Jentic to discover a source's metrics and dimensions, query the report, and download the extraction once it completes. Jentic returns the report query operation from a natural-language query, so the agent pulls the data without reading the reference first.

Discover the source's metrics and dimensions, query the report for the requested date range, then read the extraction rows once the status is complete.

Scheduled sync to a destination

Create a paused sync that pushes advertising report results to an allowed destination, then run or resume it on a cadence so a warehouse or sheet stays current. The sync operations expose pause, resume, run, and archive so a pipeline can control delivery without re-querying by hand.

Create a paused sync to the allowed destination, run it once to confirm delivery, then resume it so results push on the schedule.

Metric and dimension discovery

Discover the metrics, dimensions, and levels a report source supports before building a query, which keeps a report definition valid as sources change. Analysts use the catalog to assemble correct report requests rather than guessing field names.

Read the catalog for the chosen source, list the available metrics and dimensions, and assemble a valid report query from them.

Key Endpoints

20 endpoints — the getmcpads.

METHOD

PATH

DESCRIPTION

GET

/v1/accounts

List accounts the key may read

GET

/v1/catalog/{source}

Discover metrics, dimensions, and levels

POST

/v1/reports/query

Query a report

POST

/v1/exports

Create an extraction

GET

/v1/exports/{id}

Get extraction status

GET

/v1/exports/{id}/rows

Read a result page

GET

/v1/syncs

List synchronizations

POST

/v1/syncs

Create a paused synchronization

GET

/v1/accounts

List accounts the key may read

GET

/v1/catalog/{source}

Discover metrics, dimensions, and levels

POST

/v1/reports/query

Query a report

POST

/v1/exports

Create an extraction

GET

/v1/exports/{id}

Get extraction status

GET

/v1/exports/{id}/rows

Read a result page

GET

/v1/syncs

List synchronizations

POST

/v1/syncs

Create a paused synchronization

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the getmcpads.com advertising data API by hand means handling its organization-scoped key as a bearer token, polling asynchronous extractions, and coding the catalog, query, and sync calls yourself. Through Jentic you install once, import the API from the API Directory, store the key once, and your agent calls it.

Permission scoping

The API puts export and sync ids in the URL path, so a rule can bound your agent to the operations it needs, such as discovering catalogs and querying reports. You choose which operations it may call, so the sync write operations are not included unless you add them.

Credential isolation

Your getmcpads key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'query an advertising report' or 'schedule a sync', and Jentic returns the matching getmcpads operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using Get MCP Ads Data API through Jentic.

Is there a Get MCP Ads Data API MCP server?

You do not need a separate MCP server to give your agent the getmcpads.com advertising data API. Jentic connects it directly from the API Directory: import the API, store your key once, and your agent calls the catalog, report query, export, and sync operations. Operations are discovered on demand, so no extra server definitions load into the agent's context.

What authentication does the Get MCP Ads Data API use?

The API authenticates with an organization-scoped API key passed as a bearer token per its OpenAPI spec, and test keys return synthetic data for safe integration. Through Jentic the key is stored encrypted in your own Jentic One instance and supplied only when an allowed call runs, so it never reaches the agent's context.

Can I schedule a sync to a destination with the Get MCP Ads Data API?

Yes. The sync operations create a paused sync, then run, resume, pause, or archive it so report results push to an allowed destination on a cadence. Polling and downloads do not consume additional request credits.

What are the rate limits for the Get MCP Ads Data API?

The OpenAPI spec does not state fixed rate limits, and overages are blocked rather than throttled. A usage endpoint reports your current consumption and limits, and you can confirm the account caps in the getmcpads documentation at https://getmcpads.com.

Can I limit what my agent is allowed to do with the Get MCP Ads Data API?

Yes. Write a rule that permits only the read operations, discovering catalogs and querying reports, when the agent should only report, and add the sync write operations only for workflows that actually schedule deliveries, with every call logged.

How do I query an advertising report with the Get MCP Ads Data API through Jentic?

Search Jentic for 'query an advertising report' to surface the report query operation, load its input schema, pass the source, metrics, and date range, and execute, then read the extraction once it completes. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Get MCP Ads Data API

AI ReadinessFoundational (C)56/100

See full scorecard

Official vendor OpenAPI document · agent-readyAnalyticsBusiness Intelligencebearer20 EndpointsREST

For Agents

Pull and deliver advertising report data: discover metrics and dimensions, query reports, create and download extractions, and schedule syncs that push results to allowed destinations.

Use for: Query an advertising report for a date range, Discover which metrics and dimensions a report source supports, Create an extraction and download its results, List the accounts this key is allowed to read

Not supported: Does not create or edit ad campaigns, manage budgets, or place bids. Use for querying advertising reports and syncing the results to destinations only.

The getmcpads.com advertising data API delivers shared advertising reports, authenticated downloads, and scheduled data syncs. It lists the accounts and report sources a key may read, discovers the metrics, dimensions, and levels available for a source, and queries a report where larger requests return an asynchronous extraction. Completed extractions expose their status, immutable result pages, and a full download, while scheduled syncs push report results to allowed destinations on a cadence. A usage endpoint reports consumption and limits, and test keys return synthetic data for safe integration. It is aimed at analysts and tools that need advertising report data pulled or delivered on a schedule.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

97%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

70%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

53%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B-Signals: 1

61%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Get MCP Ads Data API to your agent

Capabilities

Start building with Get MCP Ads Data API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Get MCP Ads Data API

Jentic AI Readiness Score

Get MCP Ads Data API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness