Skip to main content
Glama

GrowVib: Social Media Growth

recommend_service

Read-onlyIdempotent

Choose WHICH plan option to order, once you know what to buy and for how many. Use it instead of comparing options yourself from search_catalog or get_service. Takes a service (or a platform plus a goal), a quantity, an audience and a preference. Returns one recommended option plus the cheapest, highest-tier and fastest-listed alternatives. Each pick carries the price per 1000, the total for this quantity, the quantity range it accepts, its quality tier, typed axes such as country or watch length, the listed delivery speed and start window, a sensitive flag marking a deliberate product such as a negative reaction, and short reasons written for the buyer. Branch on the typed fields; the reasons are prose in the requested locale and state only what an option gives, so their absence is never a drawback. One reason states how many independent delivery pools can serve the option, when two or more can: it is a count of the ways we can deliver it, not a promise about any one order, and a pick without it is not worse. The response also says how many options were considered, how many fit, and why the rest fell out (rejected: audience_mismatch, quantity_below_min, quantity_above_max, dominated). It carries quoted_at and catalog_version: the version fingerprints THIS service's option data the answer came from, so it differs between services and is only comparable with another answer for the same service. If you recommend, ask the user, then order, re-call for that service and compare catalog_version to know whether the card changed in between. Prices are live at order time; placing an order re-prices from the same data get_quote does, so treat quoted_at as when this answer was computed, not as a price hold. tradeoffs compares each alternative with the lead as data (price and total deltas, quality steps, listed speed ratio, start bucket delta, max quantity delta, plus gives and costs naming the dimensions it wins and loses on; null means one side lists nothing). Use it to CHOOSE and to explain a choice as what each option gives ("$18.60 less for one tier lower and twice the listed rate"); never present a pick to the user as a percentage more expensive than another. Identify the service by service_id (from search_catalog) OR by platform + goal (the deliverable, e.g. platform "youtube" and goal "short-views" or "followers"). Read-only: it places no order. Pass the returned option_id as 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).

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": {
      "quantity": "<quantity>"
    },
    "name": "recommend_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalNoThe deliverable: a metric key (followers, likes, views, short-views, members, comments, ...) or a service slug without the platform prefix (comment-likes, reel-views, story-views). Spaces and underscores are read as hyphens. Used with platform when service_id is omitted; when nothing matches, the error names the goals that platform sells.
localeNoLanguage of the option labels and the reasons: en (default), fa, ru, uz or id. The typed fields are locale-independent, so pass the user's language freely.
audienceNo"worldwide" (default) for untargeted delivery, or "<axis>:<value>" such as "country:usa" or "emoji:❤️". On a vote service the poll answer is an audience too ("answer:option-2", "answer:yes"): ask the user which answer, never assume one. The response lists the audiences the service serves.
platformNoPlatform key (telegram, instagram, tiktok, youtube, ...). Used with goal when service_id is omitted.
priorityNo"balanced" (default), "cheapest", "quality" or "fastest": which pick leads. fastest ranks on the LISTED start window first, then the listed delivery rate (the listing's own claims): for the quantities an agent usually buys the start matters more than the rate; when no eligible option lists either it falls back to balanced.
quantityYesThe quantity the user wants to order; every pick accepts it.
service_idNoThe service id or its slug (e.g. telegram-members) from search_catalog. Optional when platform and goal are given.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / service_id / description
      Previous value: -"The service id from search_catalog. Optional when platform and goal are given."New value: +"The service id or its slug (e.g. telegram-members) from search_catalog. Optional when platform and goal are given."
  2. Changed1 schema field changed
    • changedInput schema / properties / priority / description
      Previous value: -"\"balanced\" (default), \"cheapest\", \"quality\" or \"fastest\": which pick leads. fastest ranks on the LISTED delivery rate then start window (the listing's own claims); when no eligible option lists either it falls back to balanced."New value: +"\"balanced\" (default), \"cheapest\", \"quality\" or \"fastest\": which pick leads. fastest ranks on the LISTED start window first, then the listed delivery rate (the listing's own claims): for the quantities an agent usually buys the start matters more than the rate; when no eligible option lists either it falls back to balanced."
  3. Changed1 schema field changed
    • changedInput schema / properties / goal / description
      Previous value: -"The deliverable metric key (followers, likes, views, short-views, members, comments, ...). Used with platform when service_id is omitted."New value: +"The deliverable: a metric key (followers, likes, views, short-views, members, comments, ...) or a service slug without the platform prefix (comment-likes, reel-views, story-views). Spaces and underscores are read as hyphens. Used with platform when service_id is omitted; when nothing matches, the error names the goals that platform sells."
  4. Changed1 schema field changed
    • changedInput schema / properties / audience / description
      Previous value: -"\"worldwide\" (default) for untargeted delivery, or \"<axis>:<value>\" such as \"country:usa\" or \"emoji:❤️\". The response lists the audiences the service serves."New value: +"\"worldwide\" (default) for untargeted delivery, or \"<axis>:<value>\" such as \"country:usa\" or \"emoji:❤️\". On a vote service the poll answer is an audience too (\"answer:option-2\", \"answer:yes\"): ask the user which answer, never assume one. The response lists the audiences the service serves."
  5. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and destructiveHint=false, but the description goes well past them: it states plainly "Read-only: it places no order", explains that prices are live at order time and re-priced by get_quote, and warns that quoted_at is a computation timestamp, not a price hold. It also explains catalog_version scoping and the pool-count reason caveat so an agent will not over-read either field.

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 purpose and the sibling alternative, which is right, but the rest is a single dense block that mixes return-field documentation, business rules, downstream routing and presentation style guidance. Most sentences carry real information, yet the mass of caveats about reasons and pool counts makes it slower to scan than it needs to be.

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?

There is no output schema, so the description carries the return contract, and it does: the lead pick plus cheapest/highest-tier/fastest alternatives, per-pick fields (price per 1000, total, quantity range, tier, typed axes, speed, sensitive flag), the rejection reasons, and the tradeoffs structure. Nothing an agent needs in order to call or interpret it is missing.

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 baseline is 3, but the description genuinely adds semantics: the service_id OR platform+goal identification fork, what audience means on a vote service ("ask the user which answer, never assume one"), and how priority="fastest" ranks listed start window before listed rate with a balanced fallback. These are ranking rules the schema does not spell out.

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?

Opens with a specific verb and resource ("Choose WHICH plan option to order") and immediately bounds the case ("once you know what to buy and for how many"). It explicitly names the siblings it replaces, search_catalog and get_service, so an agent can distinguish it without reading either 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?

Gives explicit when-to-use ("Use it instead of comparing options yourself from search_catalog or get_service") and when-to-call downstream ("Pass the returned option_id as service_option_id to get_quote and create_paid_order ... or create_checkout when a person will pay in their own wallet"). It also prescribes the call sequence: recommend, ask the user, order, then re-call and compare catalog_version.

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