Skip to main content
Glama

update_product

Idempotent

Update specific fields of an existing product using an API key. Only passed fields are changed; omitted fields remain unchanged.

Instructions

Update fields on an existing product. Requires an API key.

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.

The API key must own the product. Trying to update someone else's product returns a 403/404.

Args: api_key: Partle API key (prefix pk_). 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). currency: New currency symbol. url: New merchant URL.

Returns: The updated product record (full, not just the changed fields).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyYes
product_idYes
nameNo
descriptionNo
priceNo
currencyNo
urlNo
Behavior5/5

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

Annotations already indicate idempotent, but the description adds key details: partial update (only passed fields change), idempotency, and error conditions. This goes beyond the minimal annotations.

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?

Well-structured with clear sections, each sentence adds value. No redundancy or filler. Efficiently covers all necessary information without being overly verbose.

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?

Despite lack of output schema, description specifies return value (full updated product). Covers usage, parameters, errors, and auth. Sufficient context for an agent to use correctly alongside sibling tools.

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?

Input schema has 0% coverage, but the description provides a comprehensive Args section explaining each parameter's format, source, and constraints (e.g., price in whole units, `pk_` prefix for API key). Fully compensates for schema gaps.

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 clearly states the tool updates an existing product with specific verb and resource. It distinguishes from `create_product` for new listings, making the purpose unambiguous.

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?

Explicitly tells when to use (update existing product) and when not to (use `create_product` for new). Also specifies requirements like API key ownership and potential errors (403/404).

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/rubenayla/partle'

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