Error during tool execution
Error during tool execution
Symptom: Everything was working fine, then multiple tools start returning “Error occurred during tool execution” — or all tool calls fail uniformly. No single tool is broken; they all are.This is almost never a server-side issue. It’s a known quirk with how Claude manages MCP connector sessions. The connection occasionally enters a stale state on Claude’s side, and requests stop reaching HireOtto’s server entirely.Fix: disconnect and reconnect the Otto connector
- Go to claude.ai/customize/connectors
- Disconnect the HireOtto connector
- Reconnect it
- Try any tool call again
No accounts showing up after authentication
No accounts showing up after authentication
Symptom: You completed the Google OAuth flow, but When you reach the account selection screen after Google sign-in, select the accounts you want to work with (you can select all or pick specific ones) and confirm the save before returning to your client.Other causes:
list_accessible_accounts returns empty, or HireOtto says no accounts are found.The most likely cause: you completed OAuth but didn’t select and save accounts on the account selection screen. The OAuth consent and the account save are two separate steps — completing one doesn’t complete the other.Fix:- You authenticated with a Google login that doesn’t have access to any Google Ads accounts. Sign in to ads.google.com with the same account to confirm.
- Your campaigns are under a Manager account (MCC) that’s nested two levels deep. HireOtto resolves one level down automatically — for deeper hierarchies, you’ll need to connect a separate Google login with direct access to the inner MCC. See the Authentication guide.
MCP server not connecting
MCP server not connecting
Symptom: Your AI client reports it can’t find the MCP server, or shows “Could not connect to MCP server.”Check the endpoint URLThe URL must be exactly:Common mistakes: trailing slash, missing
s in https, typo in the hostname.Authentication errors
Authentication errors
Symptom: “Authorization required”, “Not authenticated”, or HireOtto returns an auth URL you haven’t clicked yet.Complete the one-time OAuth flow:
- Your AI client should show an authorization URL. If it doesn’t, trigger it:
- Open the URL, sign in with the Google account that has access to your Google Ads, and complete the consent screen.
- On the account selection screen, select and save your accounts.
- Return to your client and retry.
Insufficient permissions or access denied
Insufficient permissions or access denied
Symptom: “Insufficient permissions”, “Access denied”, or “You don’t have permission to perform this action.”Check the authorized accountSign in to ads.google.com with the same Google account used during OAuth. If you can’t see the campaigns you’re trying to manage, you authorized the wrong account. Re-authenticate with the correct one:Check your user roleGoogle Ads enforces role-based permissions:
If you’re Read-only, you can pull reports and list campaigns but cannot create campaigns, modify budgets, or add keywords. Contact the account owner to upgrade your role.
| Role | Read | Write (create, update, pause) |
|---|---|---|
| Read-only | Yes | No |
| Standard | Yes | Yes |
| Admin | Yes | Yes |
Campaign creation fails
Campaign creation fails
Symptom: Campaign creation returns an error or the campaign doesn’t appear in Google Ads.Check account standingGoogle blocks campaign creation if there are billing issues, policy violations, or the account is suspended. Check at ads.google.com:
- Valid payment method on file
- No policy violation warnings
- Account not suspended
Still stuck?
Email [email protected] with:- Your Google Ads Email address
- The exact error text from the tool output
- What you were trying to do when the error occurred