Skip to main content
Glama

BravoDM

by com.bravodm
OverviewDiscussionsAdmin

Price a brand deal

price_deal
Read-only

Price a creator brand deal with BravoDM's published pricing model, the same model the free calculator at bravodm.com/tools/pricing-calculator runs. Two deal kinds: a posted deal (the creator posts on their own account; pass the follower band, niche, deliverable quantities, and the usage and exclusivity terms), and a content-only UGC deal (pass mode "ugc" and a ugc_tier; the creator films and the brand posts, so the price follows the creator's experience tier and never a follower count, and only the ugcVideo quantity prices). Returns the line-by-line price and the three numbers BravoDM publishes for a package: the floor, your number, and the strong ask, in USD.

Input Schema

NameRequiredDescriptionDefault
liveNoQuantity of live deliverables.
modeNoDeal kind. "posted" (the default) prices a deal the creator posts, off the follower band. "ugc" prices a content-only deal the brand posts, off the ugc_tier experience tier. Passing ugc_tier without a mode also selects the UGC path.
nicheYesPricing model niche key: beauty (Beauty and skincare), fashion (Fashion), fitness (Health and fitness), food (Food and drink), travel (Travel), parenting (Parenting and family), finance (Finance and business), tech (Tech and software), lifestyle (Lifestyle), entertainment (Comedy and entertainment), gaming (Gaming), other (Other).
usageNoUsage rights term key: none (No usage rights), 30d (30 days), 90d (90 days), 180d (180 days), 12mo (12 months), forever (Forever). Defaults to none.
carouselNoQuantity of carousel deliverables.
feedPostNoQuantity of feedPost deliverables.
platformYesPlatform the deal runs on: instagram, tiktok, or youtube.
storySetNoQuantity of storySet deliverables.
ugcVideoNoQuantity of ugcVideo deliverables.
ugc_tierNoUGC experience tier key (pricing model v1.1): first-deals (First deals: New to paid UGC work, building a portfolio), steady (Steady brand work: Regular paid UGC work for brands), proven (Proven performer: A track record brands ask for by name). Only read for a content-only UGC deal (mode "ugc"); defaults to first-deals, the calculator's own default.
engagementNoEngagement level key: lower (Lower than most), average (About average), above (Above average), way-above (Way above average). Defaults to average.
shortVideoNoQuantity of shortVideo deliverables.
storyFrameNoQuantity of storyFrame deliverables.
exclusivityNoExclusivity term key: none (No exclusivity), 30d (30 days), 90d (90 days). Defaults to none.
ytDedicatedNoQuantity of ytDedicated deliverables.
whitelistingNoTrue when the brand may run the content from its own handle (whitelisting, also called Spark or partnership ads). Raises the usage line.
follower_bandNoFollower band key from the pricing model: under-5k (Under 5k), 5k-10k (5k to 10k), 10k-25k (10k to 25k), 25k-50k (25k to 50k), 50k-100k (50k to 100k), 100k-250k (100k to 250k), 250k-500k (250k to 500k), 500k-1m (500k to 1M), 1m-plus (1M+). Required for a posted deal. A content-only UGC deal (mode "ugc") prices on ugc_tier instead and ignores it.
typical_viewsNoTypical views per video. Only used for YouTube pricing, where it can raise the dedicated video rate above the band base.
ytIntegrationNoQuantity of ytIntegration deliverables.
package_discountNoTrue to apply the model's 10 percent package discount on the content subtotal.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

readOnlyHint=true is consistent with a pure calculation tool, so no contradiction. The description adds genuine value beyond the annotation by disclosing the return shape: line-by-line price plus the three published numbers (floor, your number, strong ask) in USD, and by noting that UGC pricing never uses follower count.

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?

Purpose and the two-mode split are front-loaded, and every clause carries information. The middle sentence is dense and run-on, which makes it slightly harder to scan than an ideally structured description.

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

Completeness5/5

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

For a 20-parameter pricing tool with no output schema, the description covers what it computes, how the two modes differ, which inputs matter per mode, and what the response contains including currency. Nothing an agent needs to invoke it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds cross-parameter meaning the schema only repeats per-field: which parameters are read in each mode (follower_band ignored for UGC, only ugcVideo priced for content-only deals) and the mode-selection interaction with ugc_tier.

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 and resource ("price a creator brand deal") plus the exact model it runs and the two deal kinds it supports, so the operation is unambiguous. It does not explicitly differentiate from the siblings rate_benchmarks or lookup_brand_program, which an agent could plausibly confuse with pricing, keeping it below a 5.

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?

Explains the two modes and what to pass for each: posted deals take follower band, niche, deliverable quantities, usage and exclusivity, while UGC deals take mode "ugc" plus ugc_tier. That is clear routing between the tool's two paths, but there is no guidance on when to choose this over the sibling benchmark or brand-program tools.

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

All BravoDM toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources