Skip to main content
Glama

askr_upsert_products

Publish or update selected products in the Askr store tied to your agent's catalog key without altering other products; use dry_run to preview changes before publishing.

Instructions

Publish or update products in the Askr store this agent's catalog key writes. Only the given products change; every other product stays as it is. Unchanged products are not republished. Returns the ids created, updated and unchanged.

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": {
      "products": "<products>"
    },
    "name": "askr_upsert_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNoReport what would change, publish nothing.
productsYesProducts, at most 200 per call. Each: d (the product id, unique in the store), title, price {amount as a decimal string, currency}, and optionally summary, description, images (https), url (the product page, https, on one of the store origins or link origins, else not shown), topics, attrs, options, variants, visibility.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.61

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden well: it discloses that only the given products change, that untouched products are left alone, that unchanged products are not republished (idempotent-ish semantics), and what the response reports. It still omits failure/atomicity behavior on partial batch errors, permission or catalog-key requirements, and any rate/size limits beyond the schema's maxItems.

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?

Four short sentences, front-loaded with the action and scope, then the non-destructive guarantee, then the return shape. No filler or restatement of the tool name.

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 a large nested payload and no output schema, the description covers identity of the operation, change scope, and return summary. Missing is any statement about permissions, partial-failure semantics, or when to prefer the preview sibling, which matters for a publish operation against a live store.

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 description coverage is 100% and the products array is thoroughly documented inline (d, title, price, images, variants, visibility), so the baseline is 3. The description adds useful meaning to `d` (product id unique in the store) and a behavioral note that url must be on a store origin "else not shown," but dry_run itself is only described in the schema, not in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Publish or update products in the Askr store") plus the scoping qualifier "this agent's catalog key writes." An agent knows immediately this is the catalog write path, distinct from hide/set_policy siblings, though it never names an alternative tool explicitly.

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?

Usage is implied by the upsert/PUBLISH framing and the partial-change guarantee, but there is no explicit when-to-use vs when-to-use-something-else guidance. Notably, a sibling named askr_preview_diff exists and the schema exposes a dry_run flag, yet the description never routes the agent to preview or explains the relationship between the two.

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