Skip to main content
Glama

update_product

Idempotent

Update an existing product listing. Only provided fields are changed.

Authenticated. OAuth (scope `products:write`) preferred; `api_key` accepted
as fallback.

Only fields you pass are changed; omitted fields are preserved.
Idempotent — calling twice with the same input yields the same final
state. For creating a new listing, use `create_product` instead.

Caller must own the product. Trying to update someone else's product
returns an error.

Args:
    product_id: ID of the product to update. Get from `create_product`'s
        return value, `get_my_products`, or `search_products`.
    name: New product name. Omit to leave unchanged.
    description: New description. Omit to leave unchanged.
    price: New price in whole currency units (e.g. 15.99 = €15.99). Max
        100000. Omit to leave unchanged.
    currency: New currency symbol. Omit to leave unchanged.
    url: New merchant URL. Omit to leave unchanged.
    api_key: Optional API key (`pk_*`, generate at /account).
        Used when there is no OAuth token, and also when the OAuth
        token lacks the required scope — an explicitly passed key
        overrides an ambient token that is scoped too narrowly.
        An invalid or revoked token still fails regardless. Omit when using OAuth.

Returns:
    The updated product record (full, not just the changed fields), or
    ``{"error": ...}`` on auth/ownership/validation failure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNo
nameNo
priceNo
api_keyNo
currencyNo
product_idYes
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / api_key / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / api_key / default
      Added value: +null
    • removedInput schema / properties / api_key / type
      Removed value: -"string"
    • changedInput schema / required
      Previous value: -[
      -  "api_key",
      -  "product_id"
      -]New value: +[
      +  "product_id"
      +]
  2. Added

TDQS

A5/5.0
Behavior5/5

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

Beyond the idempotentHint annotation, the description details the partial-update behavior, idempotency semantics, authentication options (OAuth vs api_key), and the fallback behavior when a token lacks scope. It also discloses ownership restrictions and error conditions, going far beyond what annotations alone convey.

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 well-structured with clear sections (overview, auth, behavior, args, returns). While lengthy, every sentence adds valuable information and no content is redundant or unnecessary.

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?

Comprehensive for a mutation tool with no output schema: it explains auth requirements, ownership, idempotency, parameter behavior, and the exact return value (full updated record or error). The description leaves no meaningful gaps for an agent to operate effectively.

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?

Despite zero schema description coverage, the description thoroughly explains each parameter, including units for price (whole currency units, max 100000), meaning of 'omit to leave unchanged', and the nuanced api_key fallback logic. This fully compensates for the schema's lack of descriptive text.

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?

Clearly states the tool updates an existing product listing, specifying that only provided fields are changed. It distinguishes itself from create_product by explicitly directing users to create_product for new listings.

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

Usage Guidelines5/5

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

Provides explicit guidance on when to use this tool versus create_product, and notes the ownership requirement. This gives agents clear decision-making criteria for selecting the appropriate tool.

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.