Skip to main content
Glama

n11_product_detail

Fetches full details for one n11.com product from its URL or /urun/ path, including price, stock, rating, reviews, seller, category, description, and images.

Instructions

Detail of one product: name, brand, price in TRY, list price, stock status, rating and review count, seller (company, store name, authorized-store badge, grade), category path, description, images. product: a full product URL or site path containing "/urun/…" (find one with n11_search first), e.g. "/urun/apple-iphone-17-pro-max-256-gb-apple-turkiye-garantili-100816929".

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": "<product>"
    },
    "name": "n11_product_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
productYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that results include TRY pricing, stock status, seller badges, ratings, and images, but these are largely return-shape details and it does not explicitly state read-only behavior, error handling, or rate-limit context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with what the detail contains and then explains the single parameter. The field enumeration is somewhat long and partly duplicates the output schema, but it helps an agent decide whether to call the tool and is not padded.

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 one-parameter retrieval tool with an output schema, the description covers both what the tool returns at a high level and exactly how to supply the product argument. Only edge-case behavior for invalid URLs or missing products is absent, which is a minor gap.

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?

Schema description coverage is 0% and the schema only defines a bare string parameter. The description compensates fully by specifying that product must be a full product URL or site path containing /urun/, gives an example, and tells the agent to obtain it via n11_search.

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 resource and scope: detail of one product, then enumerates the fields returned. It also points to n11_search for obtaining the URL, which helps distinguish it from the broad search sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear prerequisite: find a product with n11_search first, then call this with a URL or path containing /urun/. It does not spell out when to prefer n11_product_reviews or n11_price_stats instead, so explicit alternatives are missing.

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