Skip to main content
Glama

Pay: Listing and delisting events

get_listing_events

Use for Binance listing and delisting events from the last 48 hours only. For all Binance announcements use get_latest_announcements. Binance listing and delisting events from the last 48 hours, newest first: token listings, trading pairs, futures launches, delistings, pair removals and collateral eligibility. Includes pairs, announcement and capture times, and AI crypto-impact scores where available. In full or compact, event_types uses trading_pair_added for a new pair and collateral_eligibility for eligible collateral. Filter by coin.: returns a JSON object with count and items. Call without payment to see the price and matching count; pay to get the records. Parameters combine as filters: limit: 1-100, default 50; coin: optional case-insensitive ticker; call list_supported_coins or GET /v1/coins for recent labels; q: optional keyword search in headline titles, 2-60 characters; since: optional UTC timestamp ending Z; before: optional next_before cursor for the next older page; format: compact or omit for full fields. Costs $0.01 USDC via x402; without payment returns an offer. No account or API key required. USDC on Base or Solana. Invalid, empty or stale requests are refused before payment. Retrying the same payment reuses a remembered settlement when its record is available; availability is not guaranteed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_listing_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoOptional keyword or phrase, 2 to 60 characters, matched case-insensitively in the headline title, such as ETF or rate cut. A paid request with no matching headline is refused before any charge.
coinNoOptional ticker such as BTC, ETH, NVDA or EURUSD, matched against the AI-tagged coins and the tickers named in each record. Call list_supported_coins or GET /v1/coins for recent labels.
limitNoMaximum records to return, 1 to 100. Default 50.50
sinceNoOptional UTC time such as 2026-11-13T09:00:00Z: only records first seen after it, so a bot polling every hour pays for new items only.
beforeNoOptional page cursor: pass next_before from the previous response to get the next older page of the same query. A response carries next_before while older matching records remain.
formatNoOptional compact view: retain selected headline or market fields and omit other fields. Omit for the full response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / before
      Added value: +{
      +  "description": "Optional page cursor: pass next_before from the previous response to get the next older page of the same query. A response carries next_before while older matching records remain.",
      +  "maxLength": 400,
      +  "pattern": "^[A-Za-z0-9_-]{4,400}$",
      +  "type": "string"
      +}
    • addedInput schema / properties / q
      Added value: +{
      +  "description": "Optional keyword or phrase, 2 to 60 characters, matched case-insensitively in the headline title, such as ETF or rate cut. A paid request with no matching headline is refused before any charge.",
      +  "maxLength": 60,
      +  "pattern": "^[A-Za-z0-9 .,'&$%+/-]{2,60}$",
      +  "type": "string"
      +}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the paid flow: $0.01 USDC via x402, USDC on Base or Solana, no account or API key, an offer returned without payment, refusal before charge for invalid/empty/stale requests, and settlement reuse on retry (explicitly not guaranteed). This is exactly the extra context the openWorldHint/readOnlyHint annotations cannot carry.

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

Conciseness3/5

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

Front-loaded with the scope and the alternative, which is good, but the text is long and repetitive (the 48-hour framing appears twice) and contains rough artifacts such as 'Filter by coin.: returns a JSON object' that make it harder to parse. Sentences mostly earn their place, but the duplication and the misplaced event_types discussion cost clarity.

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 paid, open-world tool with no output schema, it covers the return shape (count and items), the fields included, the payment mechanics, and pagination via next_before. The only real gap is the event_types discussion, which is not backed by any schema parameter and could confuse an agent about what it may filter on.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description still adds value by stating that parameters combine as filters and by framing 'since' as a polling mechanism so paying bots only buy new items. It also clarifies the compact-vs-full tradeoff, though its 'event_types uses trading_pair_added...' note refers to a field that is not a parameter, which muddies the mapping.

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?

States the specific resource (Binance listing/delisting events), the scope (last 48 hours only), and the sibling it is not (get_latest_announcements for all announcements). An agent can distinguish it from nearby announcement tools without opening a schema.

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

Usage Guidelines5/5

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

Explicitly names the alternative tool and the condition that selects it, defines the 48-hour window as a hard boundary, and adds a call-without-payment mode to preview price and matching count before committing. Nothing about when to choose this tool is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources