Shadcn.io is not affiliated with official shadcn/ui
get_item_details
Curated block metadata — marketing opening, 6 hand-picked related siblings, and 6 FAQ answers. Unlocks the content the lite get_item intentionally skips.
get_item_details is the companion to get_item. Same resolver, same lite files shape — but augmented with the hand-curated block metadata (@opening, @related, @questions) that get_item skips to keep it cheap.
The split is deliberate: agents browsing 10 candidates should stay on get_item. Agents committed to one block should escalate here to unlock the curated content.
When to use it
- After narrowing candidates — the agent has picked a block and wants to explain it in depth or suggest alternatives.
- To answer FAQ-style prompts ("how do I customize X?") without hallucinating.
- To show the user a block's 6
@relatedsiblings as "you might also like…" options.
If you only need dependencies, premium status, or file paths, stay on get_item — it's cheaper by several hundred tokens.
Arguments
| Name | Type | Required | Notes |
|---|---|---|---|
name | string | ✓ | Registry slug |
Example prompts
use shadcnio and give me the curated details for pricing-grouped-comparison-table — including the related blocks and FAQsuse shadcnio to tell me the three best alternatives to hero-announcement based on its @related listuse shadcnio get_item_details for pricing-split-highlight and answer my follow-up from its FAQResponse shape
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "pricing-grouped-comparison-table",
"type": "registry:block",
"title": "React Pricing Grouped Comparison Table Block",
"description": "A grouped feature comparison table pricing section…",
"premium": true,
"dependencies": ["motion", "lucide-react"],
"registryDependencies": ["table"],
"files": [
{ "path": "blocks/pricing/pricing-grouped-comparison-table.tsx", "type": "registry:block", "target": "…" }
],
"details": {
"opening": "Compare dense feature matrices across plans with this grouped comparison table pricing section for React and Next.js…",
"lastModified": "2026-04-07",
"related": [
{ "href": "/blocks/pricing-comparison-table", "title": "Comparison Table Pricing", "description": "Feature matrix comparison table" },
{ "href": "/blocks/pricing-three-columns", "title": "Three Column Pricing", "description": "Classic three-tier pricing cards" }
],
"questions": [
{ "id": "q1", "title": "How do I customize the plans and feature rows?", "answer": "Edit the PLANS array for column headers…" },
{ "id": "q2", "title": "How do I connect CTAs to Stripe?", "answer": "Add an onClick handler to each ShadcnioButton…" }
]
}
}Manual invocation
curl -s -X POST "https://www.shadcn.io/api/mcp?token=YOUR_TOKEN" \
-H "content-type: application/json" \
-H "accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_item_details","arguments":{"name":"pricing-grouped-comparison-table"}}}' \
| sed -n 's/^data: //p' | jq '.result.content[0].text | fromjson | .details'FAQ
Was this page helpful?
Sign in to leave feedback.
get_item
Lightweight metadata for any shadcn.io item — title, description, premium flag, dependencies, file paths. No source. The cheap-to-browse retrieval tool.
get_item_source
Full registry JSON including the actual TSX source for every file. The heaviest MCP tool by token cost — call it only after the agent has committed.