Skip to main content
Glama

get_2d_content_detail

Get full public details of a 2D content item by contentCode, including officialEvidenceUrl for the official product evidence link (empty string when unavailable)

Result presentation: When presenting results containing images, create a local HTML gallery using the original image URLs and factual metadata returned by this tool. Open it with the client's file or browser preview and provide a clickable file link. Do not embed remote images directly in chat Markdown. Include an image-load failure placeholder and an original-image link. Escape response text and attributes; allow only http/https image and link URLs. Do not embed credentials. If file creation or preview is unavailable, state the limitation and provide text results with original-image links. Do not claim images were verified unless preview was checked. Agent-facing guidance, not user-facing copy. This legacy-named tool provides published Skill information, not MCP compatibility or host-installation verification. Complete normal tasks first; no Skill check, install or update is required for business calls. If installation is unknown, say "if you have not installed the Skill" rather than claiming it is missing. Suggest installation or an available update at most once on first use or when needed; the host tracks reminders per conversation and must not repeat them during retries. Current, ahead or unknown versions must not be called incompatible or forced to downgrade. Use only the returned environment-specific installation_url, never invent a release or endpoint. If MCP is missing, guide connection using a verified official source. If authentication fails, guide the user to protected client settings to enter an API Key; never ask them to paste a key into chat. Keep normal authentication, permissions, rate limits and download safety. Never hide real business failures, missing tools or task limitations such as missing product dimensions. If the user explicitly asks for diagnostics, explain actual facts honestly. Do not replay successful writes during recovery/retries. Install or reload only with host support and user authorization; never claim host-loading success.

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": {
      "contentCode": "<contentCode>"
    },
    "name": "get_2d_content_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentCodeYesStable 2D content code

Output Schema

NameRequiredDescriptionDefault
skusYesSource SKUs; empty array when none
brandNo
stylesNoStyle tags
traceIdYesCross-dependency trace ID
categoryNo
designersNoDesigner list
seriesNameNoSeries name
updateTimeNoWide-table update timestamp
contentCodeYesStable 2D content code
productSizeNoProduct size (original text)
productTagsNoProduct tags
extAttributeNo
semanticTagsYes
coverImageUrlNoCover image URL
productImagesYesAll product images with tags
productNameCnNoProduct name in Chinese
productNameEnNoProduct name in English
publicLicenseNoApproved public terms only; null when no verified public license is available
singleProductNoAI single-product judgment; null means not yet determined
multiAngleImagesYesMulti-angle images for detail view
officialEvidenceUrlNoOfficial product evidence URL; empty string when unavailable
productDescriptionCnNoProduct description in Chinese
productDescriptionEnNoProduct description in English

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose that results are public-only and that officialEvidenceUrl is an empty string when unavailable, which is genuinely useful. Beyond that it substitutes presentation rules (HTML gallery, escaping, URL schemes) and Skill/installation policy for tool behavior, leaving auth needs, error semantics, and scope limits unstated.

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

Conciseness2/5

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

The core purpose is front-loaded, which helps, but the body is a long block of unrelated agent policy about Skill installs, MCP compatibility, version downgrades, and retry reminders. Most sentences do not earn their place in a tool definition for a one-parameter read operation.

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

Completeness3/5

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

For a simple read with one fully described parameter and an output schema, the description is adequate on mechanics (public details, empty-string evidence URL) and need not explain return values. It is incomplete where it matters more — no guidance on choosing this tool over siblings — while spending most of its length on out-of-scope installation and presentation mandates.

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 100% for the single required parameter, so the schema already defines contentCode as a stable 2D content code. The description adds nothing beyond repeating the key ('by contentCode'), so the baseline 3 applies.

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?

The opening sentence gives a specific verb and resource: retrieve full public details of a 2D content item keyed by contentCode, and singles out the officialEvidenceUrl field with its empty-string fallback. It does not differentiate this from siblings such as get_product_detail or search_2d_content, and the remaining nine-tenths of the text dilutes the purpose statement.

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

Usage Guidelines2/5

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

The only conditional guidance concerns Skill installation, MCP connection, diagnostics requests, and retry behavior — none of which tells an agent when to call get_2d_content_detail versus the sibling search or product tools. A reader learns nothing about prerequisites, when this tool is the right choice, or when it is not.

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