Adspirer mcp

Skill amekala/adspirer-mcp-plugin/skills/adspirer-mcp

How to call the Adspirer MCP hub correctly — the router two-step (action "list_tools" then action "execute" with tool_name), the direct tools search_tools and get_tool_schema, per-platform account IDs, quota rules, and the budget-unit trap (Meta budgets are in cents). Load this before making any Adspirer tool call.From its SKILL.md

Install

npx -y skills add amekala/adspirer-mcp-plugin --skill adspirer-mcp

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

5.6 KB, as published. Nobody here has run it

Calling the Adspirer MCP hub

Adspirer exposes 20 top-level tools. Six of them are routers that stand in front of hundreds of platform tools. Calling a platform tool by its own name does not work — it is not in the tool list. Read this before your first tool call.

The tool surface

Call these directly, by name:

Tool	Use it for
`start_here`	New or unsure user. Free.
`search_tools`	"Which tool does X?" Semantic search over every tool.
`get_tool_schema`	Exact parameters for a tool, before you call it.
`get_connections_status`	Which ad accounts are connected, and their health. Free.
`get_usage_status`	Plan, quota, usage this period. Free.
`switch_primary_account`	Change which account is active.
`get_campaign_performance`	Google Ads performance.
`get_meta_campaign_performance`	Meta (Facebook/Instagram) performance.
`audit_conversion_tracking`	Conversion-tracking health across platforms.
`echo_test`	Connectivity check. Free.

These are routers. Never call their inner tools by name:

google_ads · meta_ads · linkedin_ads · tiktok_ads · amazon_ads · chatgpt_ads · monitoring_and_reporting · community_plugins · google_analytics · klaviyo

The router two-step

Every router takes the same three fields: action, tool_name, arguments.

Step 1 — discover. Always first. Never costs quota.

{ "action": "list_tools" }

Returns every tool on that platform with its full parameter schema.

Step 2 — execute. Use an exact tool_name from step 1.

{
  "action": "execute",
  "tool_name": "list_tiktok_campaigns",
  "arguments": { "advertiser_id": "7012345678901234567" }
}

Rules

action: "execute" without a tool_name is invalid. It returns an error. Do not retry the same call — go back to list_tools and read the real tool name.
Never pass a platform tool name as action. action is only ever "list_tools" or "execute".
search_tools and get_tool_schema are top-level. Never wrap them in action: "execute", and never route them through a platform tool. They are not platform-specific.
Never guess a tool name or a parameter. If you are unsure, call list_tools or get_tool_schema.

Finding the right tool

When you don't know which tool does the job:

search_tools with a natural-language description of the task.
get_tool_schema with the candidate names and intent set to the user's complete request, word for word. Not a summary, not a paraphrase. Pass it every time — it is how tool discovery improves.
Call the tool: directly if it's in the direct list above, otherwise through its router with action: "execute".

Budgets: the unit differs per platform

This is the single most common error. Read the row before you send a budget.

Platform	Unit	`$50/day` becomes
Google Ads	dollars (decimal)	`50.0`
Meta Ads	cents (integer)	`5000`
TikTok Ads	account currency (decimal)	`50.0`
LinkedIn Ads	account currency (decimal)	`50.0`
Amazon Ads	account currency (decimal)	`50.0`
ChatGPT Ads	dollars (decimal)	`50.0`

Meta has a second trap: a daily_budget below 100 is interpreted as dollars and silently multiplied by 100. So daily_budget: 50 books $50/day, not $0.50. Always send Meta budgets in cents and always ≥ 100.

Never convert the user's currency to USD. Send the number in the account's own currency.

Accounts

One connected account is selected automatically. With two or more active accounts you must name one — the call fails with a multi_account error that lists them.

The parameter name differs per platform:

Platform	Parameter
Google Ads	`customer_id`
Meta Ads	`ad_account_id`
TikTok Ads	`advertiser_id`
LinkedIn Ads	`account_id`
Amazon Ads	`profile_id`
ChatGPT Ads	`account_id`

Send IDs as strings, not numbers. Naming an account the user has not connected returns a 403 — it never quietly falls back to another account, so do not treat 403 as "try again without the id."

Use get_connections_status to see what is connected.

Quota

Every tool call against a platform costs one call from the user's monthly quota (Free 15 · Plus 150 · Pro 600 · Max 3,000).

Free — call these as much as you need: action: "list_tools" on any router, start_here, get_connections_status, get_usage_status, echo_test, and everything under community_plugins.

Because discovery is free, there is never a reason to guess a tool name to save quota.

When a user runs out: Plus/Pro/Max monthly plans keep working and bill per extra call; annual plans stop at the cap. Show the error message you receive — it carries the upgrade link. Do not work around a quota error or invent the data.

Tools that may not be there

google_analytics and klaviyo appear only when the user has connected that service. If you don't see the tool, the connection is missing — say so and point them at https://adspirer.ai/connections. Don't insist the tool exists.

When something fails

Read references/error-catalog.md for the known error codes and their fixes before retrying anything. Retrying an invalid call unchanged will fail the same way.