Skip to main content
Glama
Sign In
Bybit MCP Server

Bybit MCP Server

Official
by bybit-exchange
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

getMyAdDetails

Read-only

Retrieve complete details of a specific Bybit P2P advertisement by providing its item ID. Use this to inspect ad terms, status, and configurations.

Instructions

Get details of a specific P2P advertisement.

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": {
      "itemId": "<itemId>"
    },
    "name": "getMyAdDetails"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.11

TDQS

A3.6/5.0
Behavior3/5

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

The description matches the readOnlyHint annotation and does not contradict it, but it adds little behavioral context beyond what annotations already convey. It does not mention authentication, error conditions, or any restrictions on whose ads can be retrieved.

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?

The description is a single, direct sentence with no filler or redundant restatement of the tool name. Every word contributes to identifying the 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 get-by-id operation with a single required parameter and read-only annotations, the description is minimally sufficient. However, it remains incomplete because it does not clarify the meaning or source of itemId, and it offers no guidance on output or ownership scope.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for explaining itemId. It only vaguely implies itemId identifies the specific advertisement, but it does not clearly define it, state its format, or explain how to obtain it.

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 verb ('Get'), a clear resource ('details of a specific P2P advertisement'), and the singular 'specific' distinguishes it from listing siblings like getAds and getMyAds. An agent can immediately understand this is a single-record retrieval tool.

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 wording implies this should be used when a single P2P ad's details are needed, but it does not name alternatives or explain when not to use it. Unlike a strong definition, it does not mention using getMyAds to first obtain the itemId or list ads.

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