Skip to main content
Glama

dynadot_get_listing_item

Retrieve details for a single Dynadot marketplace listing using its listing ID, not a domain name. Use it after get_listings to inspect a specific listing.

Instructions

Get details for a single marketplace listing (by listing ID, not domain name).

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": {
      "listingId": "<listingId>"
    },
    "name": "dynadot_get_listing_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
listingIdYesListing ID from get_listings

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.0.0
    • removedInput schema / properties / listingId / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "string"
      -  }
      -]
    • addedInput schema / properties / listingId / type
      Added value: +[
      +  "number",
      +  "string"
      +]
  2. First observedv2.0.1

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; 'Get details' does imply a non-mutating read, which is the key behavioral signal. It stops short of disclosing what happens for an unknown or delisted listing ID, whether auth is needed, or what fields come back, so a simple read tool is only adequately covered.

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 front-loaded sentence in which every clause earns its place: the action, the resource, and the identifier constraint. There is no filler or hedging to trim.

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 read with no output schema, the definition tells the agent enough to call it correctly and to know it returns details for one listing. Only the return contents and not-found behavior are left unstated, which is a minor gap at this complexity.

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?

With one parameter at 100% schema coverage and the schema already saying 'Listing ID from get_listings', the description's restatement of the same fact adds little. The '(not domain name)' note reinforces correct input selection but does not add syntax, format, or sourcing detail beyond the schema.

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 definition names a specific verb and resource ('Get details for a single marketplace listing') and disambiguates the identifier with '(by listing ID, not domain name)'. That contrast implicitly separates it from the plural listing tools in the sibling set, though it never names the sibling it complements.

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

Usage Guidelines3/5

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

The parenthetical clarifies which input shape belongs here (a listing ID rather than a domain), which is a real use constraint. However, the description never states when to choose this over the obvious list-style sibling, leaving the agent to infer that this is the single-record follow-up call.

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