Skip to main content
Glama
Otha-Labs

Persuasion Taxonomy MCP

Diagnose marketing copy (roast / review)

diagnose_marketing_copy
Read-onlyIdempotent

Review marketing copy line by line to see which of nine reader questions it answers, where it falls short, and the main persuasion gap.

Instructions

Review, critique or roast any piece of marketing copy, whether it's an ad, a landing page, an email, a sales page, a social post or a script, and find out why it might not persuade. Before you call it, read the copy and label each line with the one reader question it mainly answers, quoting the words exactly. Those labels go in the moves array. You get back which of the nine questions the copy answers for its goal, which it answers weakly and which it skips, along with the biggest gap and what readers do when it is missing. It also checks the order, whether the answers agree with each other, and the craft, pointing to the exact words that read as machine-written, like em dashes, "it's not X, it's Y" lines and sentences that all run the same length. Then it checks the opening line and suggests techniques from the catalog to fill the gap. Use it before you show anyone a draft you wrote, and whenever someone asks "is this good?", "roast this", "what's wrong with this copy?" or "how do I make it better?"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
copyYesThe full copy, exactly as written.
goalYesWhat the copy has to get the reader to do. Use purchase when they should buy now, signup for an opt-in, a trial, a demo or a lead form, click when the whole job is the click (most ads and links), and engagement for nurture emails, newsletters and social posts that should be read, answered or followed.
briefNoThe brief, if you have it: the brand, product, offer, audience and proof. With it, the opening line gets the swap test, which asks whether a competitor could send it unchanged.
movesYesYour line-by-line labels. Quote each persuasive line exactly and name the one reader question it mainly answers. Skip lines that are pure filler.
formatYesThe kind of copy it is: ad, landing_page, sales_letter for long-form sales copy, email, email_subject, social_post, video_script or headline.
categoryNoThe industry, if you want to compare against what brands in that category usually do. There is enough data for apparel, automotive, b2b_saas, beauty_skincare, business_coaching, consumer_tech, dtc_food_bev, dtc_health, fitness_health, home_goods, info_product, investing, marketing_education, otc_pharma, personal_care, personal_development, supplements, weight_loss. Any other category still works, just without the comparison.
headlineNoThe headline or opening line, if it isn't the first line of the copy.
awareness_levelNoHow much the reader already knows, on Eugene Schwartz's scale. Use unaware if they don't know they have the problem, problem_aware if they feel it, solution_aware if they know solutions exist, product_aware if they know you, and most_aware if they're ready and only need the offer.
persuasion_modeNoHow hard the copy is allowed to push. Balanced is the default, persuasive and sustainable over time. Equity protects long-term trust, so it rules out fear, hype and hard-sell moves. Aggressive is for short-term direct response and allows fear, threat and hard scarcity. In every mode, the claims stay true.balanced

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish that this is a safe, idempotent, non-open-world read, so the barrier is low, and the description adds real behavioral value: it discloses that the caller must pre-label each line into the moves array, and what the response contains (nine-question coverage, biggest gap, order, agreement, craft/machine-written markers). It stops short of covering limits like the 80-move cap or behavior on unparseable input.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and the pre-call workflow before the description of outputs, and every clause carries information. It is a dense, long run-on paragraph, so scanning is harder than it needs to be, but there is little outright filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a nine-parameter tool with nested objects and no output schema, the description covers the purpose, the required pre-work and the shape of the result well enough to call it correctly. The remaining gap is that return structure is described narratively rather than concretely, and sibling boundaries are left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all nine parameters including enums, defaults and nesting; the baseline of 3 applies. The description reinforces the labeling workflow for moves but adds no syntax, format or constraint detail beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb set (review, critique, roast) against a specific resource (any piece of marketing copy) and enumerates the formats it covers. It does not explicitly name sibling tools it overlaps with, such as check_headlines, check_marketing_claims, or find_persuasion_techniques, even though the description claims to also do opening-line checks and suggest techniques.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear trigger conditions and even quoted user phrasings ('is this good?', 'roast this', 'what's wrong with this copy?') plus the recommended timing before showing a draft. It never states when NOT to use it or which sibling tool to pick for a narrower job.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.