Toolbooth

Token promotion check

token_promotion_check

Read-only

Whether a token has paid DexScreener for visibility: its paid orders (profile, ads, community takeover) with review status and payment date, its boost purchases, and whether it is on DexScreener's top-boosted list right now, plus that list. Paid visibility isn't organic interest: boosts and ads push a token up DexScreener's lists while they last. Solana by default; any DexScreener chain id (base, ethereum, bsc…). Fails (and is not charged) if DexScreener doesn't answer. Costs $0.001 USDC per call.

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": {
      "tokenAddress": "<tokenAddress>"
    },
    "name": "token_promotion_check"
  }
}

Input Schema

Name	Required	Description
`chain`	No	DexScreener chain id: solana, base, ethereum, bsc, arbitrum… (default solana)
`topLimit`	No	Top-boosted tokens to include, 1–30 (default 10)
`tokenAddress`	Yes	Token mint (Solana) or contract address
`includeTopBoosted`	No	Include DexScreener's current top-boosted tokens (default true)

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover the read-only and open-world profile, but the description adds material context the annotations cannot: a $0.001 USDC cost per call, and that the call fails without being charged if DexScreener does not respond. Missing only finer details such as typical latency or partial-result behavior.

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?

Four dense sentences, front-loaded with the core question and ending with cost and failure semantics, which are high-value trailing details. Slight redundancy with the schema in restating the Solana default and chain ids.

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?

With no output schema, the description usefully outlines the shape of the response (orders, review status, payment date, boosts, the top-boosted list itself). Combined with cost and failure semantics, an agent has what it needs to decide and call correctly.

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?

Schema description coverage is 100%, so all four parameters are already documented, including chain ids and the 1–30 topLimit range. The description restates the Solana default and the top-boosted list option, adding little beyond the schema, so the baseline 3 applies.

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?

Names a specific resource (paid DexScreener promotion for a token) and enumerates what is returned: paid orders with review status and payment date, boost purchases, and top-boosted list membership. This is clearly distinct from siblings like token_metadata, dex_search, or trending_tokens, which cover organic data.

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?

Usage context is implied by 'Paid visibility isn't organic interest: boosts and ads push a token up DexScreener's lists,' which tells the agent when this matters versus organic-metric tools. However, no sibling is named and no explicit when-not-to-use condition is given.

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

All Toolbooth tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?