Skip to main content
Glama

Search SMM panels

search_panels
Read-onlyIdempotent

Find SMM panels (wholesale social-media-marketing resellers) tracked by PanelCompare, ranked by score, price, trust, uptime, provider score or catalogue uniqueness, optionally filtered by platform, payment method, feature or minimum trust score. Returns each panel with its trust score (0-100), overall score (0-10), 30-day uptime, provider-meter reading and its PanelCompare page.

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": "search_panels"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNobest
limitNo
queryNoName or domain, e.g. "justanotherpanel".
featureNoA feature the panel must offer.
paymentNoPayment method slug, e.g. "paypal", "crypto", "usdt".
minTrustNoMinimum trust score.
platformNoPlatform slug the panel must sell, e.g. "instagram", "tiktok", "youtube".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / feature / enum
      Previous value: -[
      -  "api",
      -  "child-panel",
      -  "drip-feed",
      -  "refill",
      -  "cancel-button",
      -  "geo-targeting",
      -  "subscriptions",
      -  "live-chat",
      -  "free-trial",
      -  "mass-order"
      -]New value: +[
      +  "api",
      +  "child-panel",
      +  "drip-feed",
      +  "refill",
      +  "cancel-button",
      +  "geo-targeting",
      +  "subscriptions",
      +  "live-chat",
      +  "free-trial",
      +  "mass-order",
      +  "mcp"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / sort / enum
      Previous value: -[
      -  "best",
      -  "cheapest",
      -  "trust",
      -  "newest",
      -  "services",
      -  "uptime",
      -  "rating"
      -]New value: +[
      +  "best",
      +  "cheapest",
      +  "trust",
      +  "newest",
      +  "services",
      +  "uptime",
      +  "rating",
      +  "provider",
      +  "unique"
      +]
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world behavior, so the description doesn't need to repeat that. It adds real value by describing the return payload (trust score, overall score, uptime, provider-meter reading, page link) in the absence of an output schema, and explains that results are ranked. It omits the default limit of 10 and the max of 25, which is a modest behavioral gap.

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?

Two dense sentences, front-loaded with the verb, resource and parenthetical definition, with the return shape last. No filler, though the ranking sentence packs many terms without breaking them out.

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 seven-parameter, zero-required search tool with no output schema, the description covers the result payload and the ranking dimension well. The main missing piece is limit/pagination behavior, which an agent would otherwise only learn by reading the schema.

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 coverage is 71%, so the schema already documents most parameters. The description's ranking list ('score, price, trust, uptime, provider score or catalogue uniqueness') adds flavor but does not map those concepts onto the actual sort enum values like 'newest', 'rating' or 'services', so it adds only marginal meaning.

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?

States a specific verb+resource (find SMM panels tracked by PanelCompare) and explains what SMM panels are, which makes the domain unambiguous. It implies a list/search scope that contrasts with the sibling get_panel, though it never names that sibling explicitly.

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?

Phrases like 'optionally filtered by platform, payment method, feature or minimum trust score' imply when to reach for it, but there is no explicit when-to-use/when-not guidance and no mention of when to prefer get_panel or compare_service_prices instead.

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