Skip to main content
Glama

GrowVib: Social Media Growth

search_catalog

Read-onlyIdempotent

START HERE when you do not yet know which service to buy: this is the entry point to the catalog. Already have a service id? get_service returns that one in full detail. Know the service and only need the right plan for a quantity? recommend_service picks one. Searches the sellable social growth service catalog (Telegram, Instagram, TikTok, YouTube and more). Each result includes the service (id, name, platform, starting/cheapest price per 1000) AND up to 8 of its plan options (plain options first, the recommended first among them, each with id, name, price per 1000, min/max quantity; options_total says how many there are and get_service returns them all) - present the options to the user and let them choose a plan, then pass that service_option_id to get_quote and create_paid_order (this endpoint lists it while the accountless x402 payment channel is on), or create_checkout when a person will pay in their own wallet instead (listed while checkout sessions are on) instead of defaulting to the cheapest.

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_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results per page (1-50, default 50).
queryNoKeyword search over service names and descriptions. Pass concrete keywords (e.g. "telegram members"); map the user's natural-language intent (budget, country, speed) onto the structured filters below.
localeNoCatalog language for names/descriptions (default en). Each service is returned once per call in this single language.
offsetNoRow offset for paging (default 0). The response returns total, limit, offset and returned; fetch the next page with offset += limit while offset+returned < total.
countryNoFilter to geo-targeted services for a country (matches the catalog's geo-target codes, e.g. a country name or code). Most services are global and unaffected.
sort_byNoSort order: "newest" (default) or "name" (alphabetical).
platformNoFilter by platform key, e.g. telegram, instagram, tiktok, youtube.
quantityNoOptional: only list the options that accept this quantity (min_quantity <= quantity <= max_quantity). options_total still counts every option, options_fit says how many accept it, and fit_starting_price_per_1k is the cheapest of those (starting_price_per_1k is the cheapest at any quantity). Each service still shows at most 8 options (plain ones before multi-post and sensitive ones, the recommended first within each, then the cheapest; options_truncated says when some were cut), so call get_service for the full list of a service you have chosen.
max_priceNoOnly services whose starting price per 1000 is at most this (USD) - use for a budget cap.
min_priceNoOnly services whose starting price per 1000 is at least this (USD).
sort_orderNo"asc" or "desc". Defaults to desc for newest, asc for name.
speed_tierNoFilter by delivery speed tier (e.g. instant, fast) - use for "fastest delivery" requests.
quality_tierNoFilter by quality tier, e.g. standard, premium.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / quantity / description
      Previous value: -"Optional: only list the options that accept this quantity (min_quantity <= quantity <= max_quantity). options_total still counts every option and options_fit says how many accept it. Each service still shows at most 8 options (the recommended ones first, then the cheapest; options_truncated says when some were cut), so call get_service for the full list of a service you have chosen."New value: +"Optional: only list the options that accept this quantity (min_quantity <= quantity <= max_quantity). options_total still counts every option, options_fit says how many accept it, and fit_starting_price_per_1k is the cheapest of those (starting_price_per_1k is the cheapest at any quantity). Each service still shows at most 8 options (plain ones before multi-post and sensitive ones, the recommended first within each, then the cheapest; options_truncated says when some were cut), so call get_service for the full list of a service you have chosen."
  2. Changed1 schema field changed
    • changedInput schema / properties / quantity / description
      Previous value: -"Optional: only list the options that accept this quantity (min_quantity <= quantity <= max_quantity), cheapest first. options_total still counts every option and options_fit says how many accept it, so a small buyer finds its orderable options without paging through hundreds."New value: +"Optional: only list the options that accept this quantity (min_quantity <= quantity <= max_quantity). options_total still counts every option and options_fit says how many accept it. Each service still shows at most 8 options (the recommended ones first, then the cheapest; options_truncated says when some were cut), so call get_service for the full list of a service you have chosen."
  3. Changed1 schema field changed
    • addedInput schema / properties / quantity
      Added value: +{
      +  "description": "Optional: only list the options that accept this quantity (min_quantity <= quantity <= max_quantity), cheapest first. options_total still counts every option and options_fit says how many accept it, so a small buyer finds its orderable options without paging through hundreds.",
      +  "type": "number"
      +}
  4. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max results per page (1-50, default 20)."New value: +"Max results per page (1-50, default 50)."
  5. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantive behavior the annotations cannot: results bundle a service with up to 8 plan options (plain first, recommended first within each), options_total/options_truncated signal truncation and get_service returns the rest, and it notes which downstream endpoints are currently listed depending on the payment channel. That is meaningful operational context for a read tool.

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?

Front-loaded correctly: the first clause is the trigger condition, then alternatives, then what is returned. However, the second sentence is a long run-on stacking parentheticals about channel availability and option ordering, and get_service's role is restated twice, which costs some readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 13 optional parameters and no output schema, the description carries the burden for return shape and does so: it enumerates the per-service fields (id, name, platform, starting price per 1000), the option fields, and the truncation counters. It also closes the loop on how the returned service_option_id is consumed next, leaving nothing essential unspecified.

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% and the schema itself already explains limit, offset paging, quantity fit semantics, price caps, and sort defaults in detail. The description adds only a general instruction to map natural-language intent onto structured filters and to treat the option list as a capped preview; it does not deepen individual parameter meaning beyond the schema. 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?

"START HERE when you do not yet know which service to buy... entry point to the catalog" plus "Searches the sellable social growth service catalog" gives a specific verb and resource. It explicitly separates itself from get_service (full detail for one known id) and recommend_service (plan for a known service), so an agent can pick it without opening other schemas.

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?

States the selection condition for itself ("do not yet know which service to buy"), the condition for get_service ("already have a service id"), and for recommend_service ("know the service and only need the right plan for a quantity"). It also routes the follow-up step: pick an option, then pass service_option_id to get_quote/create_paid_order, or create_checkout when a person pays in their own wallet.

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