Skip to main content
Glama

Get Product

sirv_get_product
Read-onlyIdempotent

Retrieves a single product by ID, returning its catalogue fields, ordered asset URLs, and variants for review or downstream updates.

Instructions

Get one product by id: its catalogue fields (name, SKU, status, description, brand, category, type, tags and source), its linked assets in order with their URLs, and its variants.

Use it after sirv_list_products finds the id. Do not use it to search: use sirv_list_products with q. To change the product, use sirv_update_product.

Inputs: id, the product id, and orgId for a product in another workspace. An unknown id returns a not-found error. Read-only.

Credits: free.

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": "sirv_get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesProduct id, from sirv_list_products
orgIdNoWorkspace id from sirv_list_organizations. Default: the workspace you signed in to

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.1
    • changedInput schema / properties / id / description
      Previous value: -"Product ID"New value: +"Product id, from sirv_list_products"
    • changedInput schema / properties / orgId / description
      Previous value: -"Organization ID (uses default org if omitted)"New value: +"Workspace id from sirv_list_organizations. Default: the workspace you signed in to"
    • addedInput schema / properties / orgId / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description still adds real value beyond them: an unknown id returns a not-found error and the call is free (credit cost), which an agent cannot learn from the 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?

Front-loaded with the return shape, then usage rules, then inputs, then cost. Each block is a short sentence and every line carries distinct information; nothing is padding.

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?

With no output schema, the description compensates by describing the returned fields, ordered assets with URLs, and variants. Combined with the not-found behavior and optional workspace scoping, an agent has everything needed to call it correctly.

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%, so both `id` and `orgId` are already documented with their provenance and default. The description restates 'the product id' and 'for a product in another workspace' without adding new syntax or format detail, so the baseline 3 applies.

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?

States a specific verb and resource ('Get one product by id') and then enumerates exactly what is returned: catalogue fields, linked assets in order with URLs, and variants. This is far more specific than the name alone and makes it distinguishable from list/update/delete siblings.

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 routes usage: call after sirv_list_products finds the id, do not use for search but use sirv_list_products with q, and use sirv_update_product to change the product. Both the positive trigger and the exclusion are named.

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