Skip to main content
Glama

Whizbrew

Find data tools

search_tools
Read-only

Find tools among the 884 marketing data tools of Whizbrew (social profiles, posts and comments, app stores, ad libraries, trends, shops, developer and web data). Ask in plain words, e.g. "tiktok comments of a video". Returns each tool's name, one-line summary, price, group and stats (how often it worked and returned data in real calls of the last 7 days, and its median time). Between equal matches the tool that works more often comes first; a tool our health check found down comes last with its state. Free. Start here.

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

Input Schema

NameRequiredDescriptionDefault
groupNoOnly tools of one group
limitNoHow many tools to return
queryNoWhat you are looking for, in plain words
platformNoOnly tools of one platform: the part of a tool name before the dot, e.g. tiktok, ig, youtube, appstore

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: result ordering by observed reliability over the last 7 days, down tools pushed to the end with their state, and the fact that it is free. Rate limits and failure modes are not discussed, keeping it below a 5.

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 with purpose, then query style, then return contents and ranking, then cost and 'Start here.' The parenthetical domain list is slightly long but each item maps to a real enum value in the group parameter, so it earns its space.

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 correctly spells out the returned fields (name, summary, price, group, stats) and the meaning of the stats window, which is exactly the information an agent needs. Only the interaction with sibling tools for the follow-up step is left implicit.

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. The description goes beyond the schema by giving a concrete natural-language query example ('tiktok comments of a video') and by unpacking what the domain groups contain, which helps the agent form queries and pick a group filter.

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 a specific verb ('Find tools') plus the exact resource scope (884 marketing data tools of Whizbrew) and enumerates the covered domains. This clearly distinguishes it from siblings like describe_tools and call_tool, which operate on an already-chosen tool.

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

Usage Guidelines4/5

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

'Start here' and 'Ask in plain words' give clear entry-point and query-style guidance, and 'Free' signals cost. What is missing is an explicit handoff statement (e.g. use describe_tools to get a schema, call_tool to execute), so the agent must infer the downstream steps.

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