Skip to main content
Glama
bybit-exchange

Bybit MCP Server

Official

getMyAdDetails

Retrieve detailed information about a specific P2P advertisement using its item ID.

Instructions

Get details of a specific P2P advertisement.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemIdYes
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states the operation (get details) without disclosing any behavioral traits such as authorization requirements, rate limits, or what the response contains.

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

Conciseness4/5

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

The description is concise with a single sentence that gets straight to the point. No unnecessary words, though it could benefit from slightly more detail on the parameter.

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?

Given the tool's simplicity (1 param, no output schema), the description is minimal but missing critical context about the parameter and what 'details' entails. The agent might need more information to use it correctly.

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

Parameters1/5

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

Schema description coverage is 0%, but the description does not explain the meaning of the single required parameter 'itemId'. The agent has no context on what this ID represents (e.g., ad ID vs transaction ID).

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 'Get details of a specific P2P advertisement', using a specific verb and resource. It distinguishes from sibling tools like 'getMyAds' (list) and 'getAds' (likely other list) by focusing on a single ad.

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 vs alternatives like 'getMyAds' or 'getAds'. The description implies usage for a specific ad but does not explicitly state when to choose this over other ad-related tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bybit-exchange/trading-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server