paystack-mcp

update_product

Update an existing product's details, including name, price, currency, stock quantity, and description, by specifying its product ID.

Instructions

Update an existing product by ID

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

Name	Required	Description
`id`	Yes	The id of the product to update
`name`	No	The name of the product
`price`	No	The price of the product. Price should be in the subunit of the supported currency
`currency`	No	The currency of the product
`quantity`	No	Number of products in stock. This is required if unlimited is false.
`unlimited`	No	Whether the product has an unlimited quantity. Set to true if the product has unlimited stock. Leave as false if the product has limited stock
`description`	No	The description of the product

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'update an existing product by ID' without revealing partial update semantics, error behavior for non-existent IDs, required permissions, or side effects. This is insufficient for a mutation 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?

The description is a single, front-loaded sentence that is efficient and free of unnecessary words. Every word adds value to understanding the tool's core function.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations and no output schema, the description is too sparse. It does not explain update semantics (full vs. partial), required fields beyond id, behavior when the product is not found, or how the currency/price fields interact. The schema covers parameter types but not runtime behavior.

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 schema provides descriptions for 100% of the parameters, so the description does not need to add parameter-level details. The phrase 'by ID' reinforces the id parameter, but adds no new meaning beyond the schema.

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 action (update), the resource (existing product), and the required identifier (by ID). This distinguishes it from sibling tools like create_product, get_product, and list_products.

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?

The verb 'update' implies it is for modifying an existing product, but no explicit guidance is given on when to use this tool versus alternatives (e.g., create_product if the product does not exist). No exclusions or prerequisites are mentioned.

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