Adyntel MCP integration for AI agents.
Connect AI agents to Adyntel through 6 structured actions, including get domain keywords, get tiktok ad details, and search google ads. Review authentication…
- ACTION CONTRACTS
- 6
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Adyntel integration exposes
The Adyntel Agent App exposes 6 provider-backed actions for marketing and data work. Its current contract lets an authorized agent get adyntel paid and organic keyword metrics for a company domain, get details for one tiktok ad by id using adyntel, and search google ads for a company domain using adyntel's google ad library endpoint. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Adyntel account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Adyntel capabilities.
Showing 6 of 6 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_domain_keywordsREADGet Adyntel paid and organic keyword metrics for a company domain.
INPUTS: company_domain / language / limit
get_tiktok_ad_detailsREADGet details for one TikTok ad by ID using Adyntel.
INPUTS: id
search_google_adsREADSearch Google ads for a company domain using Adyntel's Google ad library endpoint.
INPUTS: company_domain / media_type / continuation_token / extract_text / data_provider
search_linkedin_adsREADSearch LinkedIn ads for a company domain or LinkedIn page ID using Adyntel.
INPUTS: company_domain / linkedin_page_id / continuation_token / extract / live_ads
search_meta_adsREADSearch Facebook and Instagram ads for a company using Adyntel's Meta ad library endpoint.
INPUTS: company_domain / facebook_url / country_code / continuation_token / media_type
search_tiktok_adsREADSearch TikTok ads by keyword using Adyntel's TikTok ad library endpoint.
INPUTS: keyword / country_code
INPUT CONTRACTS
Know what the action needs before it runs.
get_domain_keywords
company_domainREQUIRED- The company domain without protocol or www prefix, for example clay.com.
languageOPTIONAL- The language for keyword results.
limitOPTIONAL- The number of keyword results to return.
get_tiktok_ad_details
idOPTIONAL- The TikTok ad ID to fetch.
search_google_ads
company_domainREQUIRED- The company domain without protocol or www prefix, for example clay.com.
media_typeOPTIONAL- Filter Google ads by media type.
continuation_tokenOPTIONAL- The continuation token returned by a previous Adyntel response.
extract_textOPTIONAL- Whether Adyntel should extract text from ad creatives.
data_providerOPTIONAL- The Adyntel data provider to use for this request.
search_linkedin_ads
company_domainOPTIONAL- The company domain without protocol or www prefix, for example clay.com.
linkedin_page_idOPTIONAL- The LinkedIn Page ID to search for.
continuation_tokenOPTIONAL- The continuation token returned by a previous Adyntel response.
extractOPTIONAL- Return a derived LinkedIn value instead of full ads.
live_adsOPTIONAL- Whether to return only currently active LinkedIn ads.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Domain Keywords
Get Adyntel paid and organic keyword metrics for a company domain. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_domain_keywordsVerify with Get Tiktok Ad Details
Get details for one TikTok ad by ID using Adyntel. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_tiktok_ad_detailsSAFETY BOUNDARY
Operate Adyntel with explicit limits
- Authorize Adyntel with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Adyntel data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Adyntel rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Adyntel task completed successfully.
CONNECTION MODEL
API key
Adyntel API key sent as the api_key field in JSON API requests. Find it in your Adyntel profile under Integrations: https://docs.adyntel.com/authorization.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 6
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Adyntel.