Skip to main content
Glama
Garu-Pagamentos

garu-mcp

Official

update_product

Partially update a product's fields (name, price, payment methods, subscription settings) by sending only the values to change; unspecified fields remain unchanged.

Instructions

Update an existing product (partial PATCH — only the fields you provide are written; everything else keeps its persisted value). value is in decimal BRL / reais (e.g. 29.90), NOT centavos. Setting pixAutomatic: true exposes Pix Automático (BACEN auto-debit recurring Pix) on the subscription checkout. At least one write field is required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pixNoOffer PIX at checkout.
nameNoProduct name.
tagsNoFree-form tags.
imageNoHTTPS URL of the product cover image.
valueNoPrice in decimal BRL / reais (e.g. R$29,90 → 29.90) — NOT centavos. Products store the price in reais, the same as the API and dashboard.
boletoNoOffer Boleto at checkout.
productIdYesProduct identifier — accepts the UUID (preferred — same id returned by list_products and webhook payloads) or the legacy positive integer id. UUID support added in Garu v0.10.0.
returnUrlNoURL the buyer returns to after a successful payment.
unitLabelNoPer-unit label shown on the checkout (e.g. 'seat').
creditCardNoOffer credit card at checkout.
descriptionNoProduct description.
installmentsNoMax number of installments offered on credit card.
pixAutomaticNoWhen true, exposes Pix Automático (BACEN auto-debit recurring Pix) on the subscription checkout. Only the subscription checkout mode reads it.
isSubscriptionNoMark the product as a subscription (recurring).
subscriptionTypeNoSubscription cadence label (e.g. 'monthly').
returnUrlButtonTextNoLabel for the return-URL button on the success page.
Behavior4/5

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

With no annotations, description carries full burden. It discloses PATCH behavior (only fields provided are written), clarifies value unit (decimal reais, not centavos), and explains pixAutomatic effect. Does not mention idempotency or error handling, but sufficient for an update tool.

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 concise, front-loaded sentences. Each sentence adds distinct value: purpose+patch, value clarification, pixAutomatic+requirement. No wasted words.

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?

Given 16 parameters, full schema coverage, no output schema, and no annotations, the description covers key nuances (partial update, value format, pixAutomatic, required field). Could mention idempotency or default behaviors, but overall complete enough.

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

Parameters5/5

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

Schema coverage is 100%, baseline 3. Description adds significant value: clarifies value format with example, explains pixAutomatic behavior, and notes the required write field condition. These details go beyond the schema descriptions.

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?

Description clearly states 'Update an existing product (partial PATCH)' with a specific verb and resource. It distinguishes from sibling tools like create_product and list_products, and the partial update behavior is explicit.

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?

Description implies when to use (to modify existing product) and states a requirement ('At least one write field is required'). It does not explicitly contrast with alternatives but the context is clear. Lacks explicit when-not guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Garu-Pagamentos/garu-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server