Skip to main content
Glama

Montar post de oferta

create_offer_post
Read-only

Monta um post de oferta pronto para publicar (título, preço, cupom e link final) a partir de uma ou mais URLs de produto, usando o template de oferta do bot. OBRIGATÓRIO informar "url" ou "urls". Informe "coupon" para incluir um cupom no post. Devolve o TEXTO formatado (não JSON).

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": "create_offer_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
ctaNoOpcional. CTA (chamada para ação) que aparece onde você posicionar a variável {cta} no formato; sem {cta} no formato, não aparece. Ex.: "Compre aqui 👇".
urlNoURL de um produto.
urlsNoVárias URLs de produto (até 20).
couponNoOpcional. Código de cupom a incluir no post.
telegram_user_idNoOpcional. ID do usuário do Telegram para tracking por usuário.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real context beyond that: it discloses that the return value is formatted TEXT and explicitly not JSON, and that the bot's offer template is applied — both non-obvious behaviors that change how an agent consumes the result.

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?

Three tight sentences: purpose first, then the hard input constraint, then the optional coupon, then the return format. No filler, and the most decision-critical rule (mandatory url/urls) is front-loaded rather than buried.

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?

With five params, no output schema, and a text return, the description covers the essentials an agent needs to call it: required input shape, optional coupon, and output type. Minor gaps remain — it does not say which template is used or how set_template interacts with it, nor what happens on an unreachable URL — but nothing blocking 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 the baseline would be 3. The description earns above baseline by surfacing the cross-parameter constraint that url OR urls must be supplied — the schema shows required: [] with no anyOf, so this rule is not otherwise expressible. It also names coupon's effect and confirms that cta/telegram_user_id are optional, though those two are left to the schema.

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 ("Monta um post de oferta pronto para publicar") plus the inputs (one or more product URLs) and the output shape (título, preço, cupom, link final). It does not, however, distinguish itself from the sibling propose_offer_post, which an agent could easily confuse with this one.

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

Usage Guidelines3/5

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

It gives one hard rule — "OBRIGATÓRIO informar 'url' ou 'urls'" — and notes when to pass coupon, which is useful invocation guidance. But there is no statement of when to prefer this over propose_offer_post, preview_userbot_rules, or get_template, so tool selection among close siblings is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources