Skip to main content

​
Start here

First identify which layer failed:
  • The AI client cannot connect to the HireOtto MCP server.
  • The server is connected, but the marketing platform is not authorized.
  • Authorization succeeded, but the expected account or property is missing.
  • The resource is visible, but the connected role cannot perform the requested action.
  • The platform accepted the request but returned no data or rejected a field, lifecycle transition, or creative.
Read the returned error before retrying. Repeating the same request unchanged rarely fixes a permission, identifier, or platform-validation problem.

​
Error during tool execution

​
Symptom

Several unrelated tools begin returning a generic execution error at the same time.

​
Fix

  • Disconnect and reconnect the HireOtto connector or app in the AI client.
  • Enable the connector again in the current chat or agent.
  • Retry one small read request.
If only one action fails while other tools still work, treat it as a tool- or platform-specific error instead of a stale client session.

​
MCP server not connecting

Confirm that you added the correct remote HTTP endpoint and that it ends with /mcp: Common problems include a hostname typo, a missing s in https, a trailing slash, configuring HireOtto as a local or stdio server, or not enabling the connector in the current conversation.

​
The server is connected, but no tools appear

  • Complete the client-level OAuth prompt.
  • Rescan or refresh the server tools.
  • Enable the connector or app in the current chat or agent.
  • Restart or reconnect the client if its MCP tool list is cached.

​
Authentication errors

​
Symptom

The response says authorization is required, not authenticated, or returns a new authorization link.

​
Fix

  • Ask to connect the relevant Google or LinkedIn product.
  • Open the newest authorization link in the same browser session.
  • Sign in with an identity that can already access the required resource.
  • Complete consent and return to the original AI client.
  • Run a small account or property list before starting a longer workflow.
If access was revoked or the platform login or security policy changed, reconnect the service.

​
Google Ads accounts are missing

Completing Google OAuth and saving selected Google Ads accounts are separate steps. Re-authenticate, select the accounts HireOtto should save, and confirm the selection before returning to the AI client. Other checks:
  • Confirm the same Google login can open the account in Google Ads.
  • Refresh accessible accounts after Google grants or changes access.
  • If a client account is available only through a deeper manager hierarchy, connect a Google login with direct access to the relevant inner MCC or account.
  • Use a distinct profile name only when connecting a different Google login; renaming the same login does not expand access.

​
LinkedIn Ads accounts are missing

Confirm that the same LinkedIn identity can open the ad account in Campaign Manager. Then reconnect LinkedIn Ads and ask: List the LinkedIn Ads accounts I can access, including my role and write capability. If the account still does not appear:
  • Check that LinkedIn Ads access is enabled for the HireOtto account.
  • Reconnect with the LinkedIn identity that has direct access to the ad account.
  • Confirm the account is active and visible in Campaign Manager.
  • Ask for the account list again after a role or access change.

​
Insufficient permissions or access denied

Read-only access supports reporting. Creating or changing campaigns normally requires Standard or Admin access. Google can still reject an operation because of account standing, policy state, campaign type, or unsupported settings.

​
LinkedIn Ads

Viewer access supports read-only work. Creating or changing ads requires a sufficient ad-account role. Inspect the role and write capability returned for the selected account before retrying.

​
I can read LinkedIn Ads but cannot create a creative

Direct Sponsored Content and other sponsored-content workflows may also require access to the associated LinkedIn Page. Confirm Page permission, ad-account role, image eligibility, destination, call to action, and supported format in Campaign Manager.

​
Reports are empty

A valid empty response does not always indicate a broken connection. Check:
  • The account, campaign-group, ad-set, or creative IDs.
  • The date window and whether the selected objects delivered during that period.
  • Whether the connected role can access the requested data.
  • Whether the chosen metrics are compatible with the requested reporting pivot.
For LinkedIn professional demographics, allow for reporting delay and privacy suppression. Small groups may not appear, and the returned rows are directional rather than exhaustive.

​
Campaign or draft creation fails

Check billing, policy warnings, suspension state, the connected role, required fields, and supported campaign settings. If a campaign exists but a child object failed, inspect and clean up or resume from the failed step instead of recreating everything blindly.

​
LinkedIn Ads

Validate the objective, account currency, budget, dates, targeting, audience size, format, Page identity, image, destination, copy, call to action, alt text, and approval state. Create new objects as DRAFT. LinkedIn campaign creation is multi-step. A campaign group or ad set can remain after a later creative step fails. Inspect the returned IDs, confirm what exists in Campaign Manager, and resume from the failed step. Do not rerun the entire workflow blindly and create duplicates.

​
A LinkedIn status change or update is blocked

LinkedIn lifecycle rules can block edits even when OAuth is valid. Retrieve the current object and status, make sure the transition is supported, and apply only the intended field change. For company exclusions, use an additive exclusion workflow so existing targeting is not accidentally replaced.

​
Related setup pages

Connect HireOtto to an AI client LinkedIn Ads quickstart

​
Still stuck?

Email [email protected] with:
  • The HireOtto server name.
  • The AI client you are using.
  • The approximate time of the issue.
  • The non-sensitive portion of the exact error.
  • What you were trying to do and the relevant account or property ID.
Do not send OAuth tokens, passwords, or other secrets.