Skip to main content
Glama

Edit one of my products

update_my_product
Destructive

Change the title, description, tags or insert card text (material line, care instructions, warnings) of one of your print shop's products. The change shows at once wherever the product is published, and the answer gives what each changed field was before. Prices and where the product is published are changed on Printlooper. Only products from list_my_products. Needs a connected Printlooper account.

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": {
      "product_id": "<product_id>"
    },
    "name": "update_my_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoReplaces the tags the product has
titleNo
warningsNoPrinted on the insert card. At least 40 characters, or null or empty to remove it.
product_idYesproduct_id from list_my_products
descriptionNoPlain text
material_labelNoThe material line on the insert card, up to 120 characters. null or empty removes it.
care_instructionsNoPrinted on the insert card. At least 40 characters, or null or empty to remove it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare this is destructive, non-idempotent, and not read-only. The description adds useful behavior beyond annotations: changes appear immediately wherever the product is published, and the response reports each changed field's previous value. It does not explicitly discuss reversibility or partial-update semantics, so it falls short of the richest behavioral disclosure.

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 front-loaded with the core action and affected fields, then adds immediacy, return-value behavior, exclusions, product source, and account requirement. Each sentence contributes relevant information without unnecessary repetition.

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?

For a mutation tool with no output schema, the description explains the immediate effect, the return value's prior-field information, prerequisites, and excluded operations. It could be slightly more explicit about partial updates and how omissions are handled, but it is otherwise complete for correct invocation.

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?

Schema coverage is high at 86%, so the input schema already explains most parameter constraints and null-removal behavior. The description adds grouping for insert-card fields and states that product_id must come from list_my_products, but it does not add much meaning beyond the structured 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 states a specific verb and resource: changing editable fields of one print shop product. It enumerates the affected fields (title, description, tags, insert card text) and distinguishes them from prices and publication settings. An agent can identify the tool without opening the schema.

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?

It provides clear when-to-use context: edit title, description, tags, or insert-card text. It explicitly says prices and publication settings are changed elsewhere, requires a connected Printlooper account, and restricts product IDs to those from list_my_products. This routes the agent away from out-of-scope mutations.

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