MAP
Marketplace Ad Pros

Getting Consistent Results
from Claude & ChatGPT

Stop wrong-account mistakes and hallucinated data. Five proven strategies, from quick wins to advanced workflows.

5 min read 5 strategies, easy to advanced For agencies & brand owners

TL;DR

LLMs don't automatically know how to use MCP tools correctly. They can confuse accounts, hallucinate data, or call tools in the wrong order. The fix is giving them the right context up front. Start with the Server Guide (takes 10 seconds), then layer on more strategies as needed.

Why This Happens

Understanding the root cause helps you pick the right fix.

Three Reasons LLMs Get Confused

  • No built-in knowledge of your tools. Claude and ChatGPT know nothing about the MAP MCP server until you tell them. Without guidance, they guess which tools to call and in what order — and sometimes guess wrong.
  • Multiple accounts look the same. If you manage several brands, the LLM has to pick the right profile for every API call. Without explicit context about which brand you're working on, it can pull data from the wrong account or mix results across accounts.
  • Conversations drift. Over a long conversation, the LLM's context window fills up. Earlier instructions about which account to use or how to call a tool get pushed out, and the LLM starts making mistakes it wouldn't have made at the start.

Strategy 1: Load the Server Guide

The single easiest thing you can do. Takes 10 seconds and dramatically improves consistency.

Easiest — do this first

What is the Server Guide?

MAP includes a built-in tool called get_server_guide that returns a comprehensive instruction set teaching the LLM exactly how to use every tool correctly — which tools to call, in what order, what parameters to pass, and how to handle multi-account scenarios.

Think of it as an instruction manual that the AI reads before starting work.

How to use it

At the start of every conversation (or whenever you switch topics), just say:

Get the server guide from Marketplace Ad Pros before we start.

That's it. The LLM will call get_server_guide, read the instructions, and follow them for the rest of the conversation.

Pro tip: If the conversation gets long and the LLM starts making mistakes, ask it to reload the server guide. This refreshes its instructions.
Setup Time
10 sec
Effort
Per chat
Impact
High

Strategy 2: Install the Amazon Ads Skill

Give Claude persistent knowledge about MAP tools so you don't need to load the server guide every time.

Moderate — one-time setup

What is a Skill?

A Claude Skill is a set of instructions that Claude loads automatically when relevant. Once installed, Claude already knows how to use MAP tools correctly without you having to ask for the server guide each time.

How to install it

We maintain a pre-built skill for Amazon Ads workflows. Install it by telling Claude:

Install the Marketplace Ad Pros skill from https://github.com/MarketplaceAdPros/skill-amazon-ads and follow the directions in the README.

Claude will read the repository and set up the skill. After that, it will automatically reference these instructions when you ask about Amazon Ads.

Note: The skill doesn't update automatically when we add new features. For the most up-to-date instructions, combine this with Strategy 1 (loading the server guide periodically).
Setup Time
2 min
Effort
One-time
Impact
High

Strategy 3: Build Custom Skills from Wins

After a successful workflow, teach Claude to remember how it did it. This is the most powerful long-term strategy.

Moderate — do after successful workflows

How it works

After Claude successfully completes a task — pulling a report, optimizing bids, running a wasted-spend sweep — you can ask it to save what it learned as a reusable skill. Next time you ask for the same type of task, it will reference that skill automatically.

What to say

After any successful interaction, try one of these:

Make a skill for how you just pulled that report so you can do it the same way next time.
Save what you learned about optimizing bids as a skill for future use.
Create a skill for how we ran that wasted-spend analysis so I can just say "run the wasted spend sweep" next time.

Claude will save the exact tool sequence, parameters, and logic it used so it can replicate the workflow reliably.

Pro tip: The more skills you build up, the more "trained" Claude becomes on your specific workflows. Over time it becomes like a team member who knows exactly how you like things done.
Setup Time
30 sec
Effort
Ongoing
Impact
Very High

Strategy 4: One Project per Brand

For agencies managing multiple accounts, this prevents the #1 mistake: pulling data from the wrong brand.

More setup — biggest payoff for agencies

The problem with multi-brand conversations

If you manage 5 brands and talk to Claude about all of them in one conversation, it has to remember which profile ID belongs to which brand for every single tool call. As the conversation gets longer, it starts mixing them up or defaulting to whichever brand was mentioned most recently.

How to set up Projects

In Claude, create a separate Project for each brand you manage. In each project's instructions, include:

This project is for [Brand Name]. Our Amazon Ads profile ID is [ID]. Our marketplace is [US/UK/etc]. Always use this profile when pulling reports or making changes. Do not access other profiles unless I specifically ask.

Now when you open that project, Claude already knows which brand you're working on — no room for confusion.

Pro tip: Add your brand's ACOS targets, budget rules, and any other preferences to the project instructions. The more context Claude has up front, the less you need to repeat yourself.
Setup Time
5 min/brand
Effort
One-time
Impact
Very High

Strategy 5: Pick the Right Model

Not all models handle complex tool use equally well. The model you pick matters more than you'd think.

Easy — just check your settings

Model comparison for MCP workflows

MCP tool use requires the model to plan multi-step sequences, track state across calls, and interpret structured data. Here's how the current Claude models stack up:

Model MCP Tool Use Multi-Account Recommendation
Opus 4.6 Excellent Excellent RECOMMENDED
Sonnet 4.6 Good Good ACCEPTABLE
Haiku 4.5 Limited Poor NOT RECOMMENDED
Bottom line: Use Opus for anything involving multiple accounts, complex reporting, or making changes. Sonnet is fine for simple single-account queries. Haiku will struggle with MCP tool use and is not recommended.

Using ChatGPT?

If you're using ChatGPT with the MAP MCP server, use GPT-4o or better. The same principles apply — load the server guide, use projects to separate brands, and pick the most capable model available.

Putting It All Together

Quick-start checklist

Here's the recommended order. Each step builds on the last:

  1. Right now: Switch to Opus 4.6 (or at least Sonnet) in your AI client settings.
  2. Every conversation: Start with "Get the server guide from Marketplace Ad Pros."
  3. One-time: Install the Amazon Ads skill from our GitHub repo.
  4. After wins: Ask Claude to save successful workflows as skills.
  5. For agencies: Create a separate Claude Project for each brand you manage.

Ready to Get Started?

Connect your Amazon Ads accounts, load the server guide, and see the difference immediately.

Connect Your Accounts
Free to connect · AI access from $10/week · Cancel anytime
Copied to clipboard