Skip to main content
Glama
Sign In
danggn-mcp

danggn-mcp

by iamkw0n
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_listing_detail

Retrieve detailed information about a Daangn marketplace listing using its article ID, URL, or slug. Get full listing details for analysis or display.

Instructions

당근마켓 게시글 상세 정보를 조회합니다.

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": {
      "articleRef": "<articleRef>"
    },
    "name": "get_listing_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
articleRefYes게시글 ID, URL, 또는 slug (예: p7mskunj8ik8)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior1/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states that it retrieves info, without mentioning response format, error conditions, rate limits, or whether it is read-only. This is a minimal description that leaves the agent without insight into side effects or output expectations.

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?

A single, concise Korean sentence with no filler. It is front-loaded and easy to parse, exactly what a short tool description should be.

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

Completeness2/5

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

With no output schema and no annotations, the description should compensate by explaining what 'detailed info' includes (e.g., price, seller, location). It only states 'detailed info', leaving the agent uncertain about the return payload. The tool is simple, but the description is too sparse to be considered complete.

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?

The schema already has 100% coverage, describing articleRef as '게시글 ID, URL, 또는 slug (예: p7mskunj8ik8)'. The description does not add extra parameter semantics, but the schema is clear enough, so a baseline score of 3 is appropriate.

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?

Description clearly states the action '조회합니다' (retrieves) and the resource '당근마켓 게시글 상세 정보' (Carrot Market post detailed info). It distinguishes from siblings by implying a single listing detail lookup versus search or summary operations.

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?

No guidance on when to use this tool versus alternatives like search_listings or summarize_search_market. The description does not mention any prerequisites, such as needing a specific articleRef obtained from a search, nor does it contrast with sibling tools.

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

Deploy Server

Other Tools