flayr

Capture offers (Hook Studio step 1)

offers_capture

[writes flayr data · write scope] Turns what the brand sells (pasted text, or answers to the offer interview) into draft offers in its offer bank, with prices from the plan catalog, Shopify or the text. Charges Embers once per call (refunded when nothing usable comes back). Needs the Pro plan or higher. (Wraps POST /api/v2/hook-studio/offers.)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "offers_capture"
  }
}

Input Schema

Name	Required	Description
`text`	No	What the brand sells, in any words.
`source`	No
`answers`	No
`brandId`	No	A brand id from GET /api/v2/brands. Required for an account-wide key; a brand-bound key may omit it.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the write and non-idempotency annotations, it discloses the required write scope and Pro plan, the per-call Embers charge, and the refund condition when nothing usable is returned. It also clarifies that the writes produce draft offers and identifies where their prices may come from.

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

Conciseness5/5

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

The description is compact and front-loads the operation after a short scope label, then efficiently covers pricing, billing, and plan requirements. The brief endpoint note adds implementation context without repetitive 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 four-parameter write tool, it covers purpose, input modes, output destination, pricing sources, authorization and plan gating, and billing behavior. Its main gaps are the conditional input contract and, with no output schema, any indication of the response shape or how captured offers are identified for subsequent steps.

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?

The input-mode wording adds useful meaning for the sparsely documented answers array and explains the roles of pasted text and interview answers. However, it does not specify how source, text, and answers must be combined or whether either input is conditionally required, which is important because the schema marks no parameters as required.

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

Purpose5/5

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

The description specifies exactly what is created—draft offers in a brand's offer bank—and identifies the supported inputs and pricing sources. Together with "Hook Studio step 1," this clearly distinguishes the operation from offers_list and offers_update, even though those siblings are not named.

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?

It provides clear usage context by supporting either pasted text or offer-interview answers and by identifying the offer-capture stage. The Pro-plan prerequisite also aids selection, but there are no explicit when-not conditions or pointers to siblings for listing or updating existing offers.

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

All flayr tools Inspect

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

Need Help?